fleet-auditing-api-surface

To find unused package.json exports, audit your library's API surface by cross-referencing the exports map and internal src references against fleet repos. This classifies each subpath as dead, single-consumer, internal-only, or consumed for targeted pruning.

An API surface audit identifies and classifies dead or unconsumed export subpaths in a library. You need it for weekly health checks, pre-release cleanup, or bundle size optimization to safely prune unused code across a fleet.

Classify dead versus consumed library exports by cross-referencing internal src references and fleet repository usage against the exports map. This generates a ranked report categorizing subpaths into dead, single-consumer, internal-only, or consumed.

The API surface audit is strictly read-only and does not modify your library. It generates a ranked report of dead, single-consumer, internal-only, and consumed subpaths to guide human decision-making before version bumps or bundle trimming.

An API surface audit requires a fleet of repos to measure consumption impact. It reads the package.json exports map and internal src references, then cross-references fleet repos to classify subpaths and generate a health check report.