internal types can be used inside methods - verify still succeeds

Given the modules "order" and "inventory". The module order contains a package "internal" with a OrderRepository and has an interface OrderApi. The inventory module contains a service "OrderService" with a method "hasOrder".

Also we have a ModularityTest that calls verify on ApplicationModules.

We observed that the call to verify fails when we are returning the OrderRepository in the method getOrder. So far so good. However if we are just utilizing the OrderRepository inside the method but in the end return a boolean, the test does not fail.

For example:

@Autowired
private OrderApi orderApi;

public boolean hasOrder(UUID id) {
    var repository = orderApi.getInternalRepository();
    return repository.exists(id);
}

Thus according to our observation the verify test does not fully enforce that internal types cannot be used at all in another module. It only enforces that internal types cannot be used as return value (or parameters) in methods in another module.

I am aware that such a case might be a bit "searched for" (probably nobody would implement a getInternalRepository method ;D) but still think that the library might benefit from an improved validation (check that classes from other modules are not allowed at all to reference any internal class).