Repository Boundary Mapper: Public Worked Example

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+.

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 check

Read 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.