The modulefinder module does not handle relative directories properly.  The error I found is when one subpackage attempts to import from a sibling subpackage using the form

    from ..language import (
        DirectiveDefinitionNode,
        ...
    )

In this example, it would report "language.DirectiveDefinitionNode" is missing.

It correctly resolves the names when importing modules, but when an import fails because it is a variable or function, it records the name incorrectly and cannot filter it out later.

I've attached a small test case and there is a README describing the test and results.