boundary-hunter-ts

To audit TypeScript module boundaries, run a boundary analysis to detect leaked internals and over-exported APIs, enforcing minimal public surfaces and stable black-box modules across your project.

Dependency direction defines the allowed import flow between architectural layers. Enforce it during refactors or API surface minimization to prevent improper coupling and ensure modules remain stable black boxes.

Minimize the public API surface by auditing exported declarations, identifying leaked internals, and wrapping external types properly to ensure only strictly necessary interfaces are exposed.

Yes, module boundary auditing is specifically designed for large TypeScript projects, applying strict rules for layered dependency direction and encapsulation to maintain architecture governance.

The best way to detect over-exported APIs is running an encapsulation audit that identifies leaked internals and improper dependency direction, guiding refactors to achieve minimal public surfaces.

Architecture governance fails because exposing internal types breaks encapsulation, turning black-box modules into white boxes. An audit identifies these boundary violations to restore stable public APIs.