An offline reporter for a narrow, explicit monorepo snapshot. It maps workspace packages to owners, follows quoted static imports, and shows imports crossing a forbidden owner boundary. A package declaration alone is not proof that source code actually depends on another team's package.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/repository-boundary-mapper.mjs --root examples/clean --config examples/clean/config.json
node bin/repository-boundary-mapper.mjs --root examples/broken --config examples/broken/config.json
node bin/repository-boundary-mapper.mjs --root examples/incomplete --config examples/incomplete/config.json
npm run checkRead the result
The example exits are 0 (allowed), 1 (forbidden), and 2 (unsupported evidence). The config path is relative to the current directory and must resolve inside --root. --help prints usage. Standard output is one JSON report line; standard error is a human summary with counts only.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.