Repository Scanning · node9 documentation
Repository Scanning
The agent surface committed to a repository: workflows, agent settings, MCP servers and instruction files.
This is a different question from everything else in these docs. Nothing is running yet. What is being checked is the configuration a pull request can change without anyone reading it closely: a workflow that feeds a stranger's text to an agent that holds secrets, an unpinned MCP server, a token sitting in a settings file, an instruction file carrying a payload.
Scan one
node9 scan-repo . node9 scan-repo https://github.com/org/repoA local path or a GitHub URL. The same checks either way.
Machine output
node9 scan-repo . --json node9 scan-repo . --markdownJSON for a pipeline, Markdown when the destination is a pull request comment.
Gating a pull request on what it introduced
A scan that reports every finding in a repository is not useful on a pull request, because the author did not write most of them and cannot act on them. What a reviewer is actually asking is narrower.
New findings only
node9 scan-repo . --base origin/main node9 scan-repo . --base origin/main --fail-on-introduced
--base scans that ref as well and reports what the working tree introduced on top of it. --fail-on-introduced exits non-zero only for those, so a build fails for what this change added and not for what it inherited.