auditing-api-surface

To find dead exports in a package.json, analyze the exports map and cross-reference internal src usage and external consumers. This classifies subpaths as dead, single-consumer, internal-only, or consumed for governance and pruning.

Auditing API surface area across repositories requires cross-referencing each package.json exports entry with internal src usage and external consumers. This produces a ranked report classifying subpaths to identify prune candidates across the fleet.

You should audit your library's export surface before a major version bump, when trimming bundle size on an infra lib, or weekly via cron. Regular reporting identifies unconsumed subpaths suitable for pruning decisions.

No, the API surface audit is a read-only workflow designed for governance. It generates a ranked report of dead, single-consumer, internal-only, and consumed exports to inform manual pruning decisions, but never deletes code.

Yes, the export surface audit is designed to work across fleet repositories. It analyzes each package.json exports entry and cross-references internal src usage and external consumers across the fleet to classify subpaths.