SUPPLY CHAIN
Engineering
Code review and dependency agent
Parity
Reviews the diff for the bug rather than the style, and tells you which advisory in the dependency tree actually reaches your code.
Reviews the diff for the bug rather than the style, and tells you which advisory in the dependency tree actually reaches your code.
Reads a change against the surrounding code, traces whether a published vulnerability is reachable from your call graph, and stays quiet when it has nothing useful to say.
Reads a change against the surrounding code, traces whether a published vulnerability is reachable from your call graph, and stays quiet when it has nothing useful to say.
const reviewer = new NexusAgent({ role: 'code_review' });
const notes = await reviewer.review({
diff: pr.diff(),
advisories: 'reachable_only',
silentWhenClean: true
});
Published examples, reproduced verbatim. This page does not call a model.
The scanner reports 47 vulnerabilities in our dependency tree. Which ones can actually be exploited here?
Three, by reachability from your own call graph. • The XML parser advisory is reachable — you call the affected entry point directly in the import handler, with input that comes from an uploaded file. This is the one to fix today. • Two are reachable through a transitive path in the reporting job. Both are denial-of-service rather than execution, and the job runs on a schedule rather than on request, so the exposure is real but bounded. The other 44 are in code paths nothing in this repository calls — 31 are in test-only or build-time dependencies, and 13 are in unused modules of packages you do import. That is not a claim they are harmless; a future change could make one reachable. It is a claim about what is reachable from the current tree, which is what a triage decision actually needs.