Practical Notes
- README describes a multi-stage pipeline and claims triage runs in <2 seconds (zero AI tokens).
- Badges show Node.js >=18 and 113 tests passing in the README header.
How to Use Adversarial Review Effectively
Adversarial review is most useful when you can reproduce findings.
Suggested workflow:
- Run
--scan-onlyfirst to get a report and decide what’s worth fixing. - Use PR scope mode (
--pr,--pr-security) so you don’t waste time on unrelated files. - If you enable auto-fix, keep it gated: start with
--dry-runor--plan-only(both are documented in the README) and require human approval for each fix in high-risk repos.
What “Good Output” Looks Like
- A bug report includes evidence (where in code), impact, and a minimal reproduction or proof of concept.
- For security findings, look for STRIDE/CWE references and CVSS scoring (the README claims these are produced).
FAQ
Q: Is this only for security? A: No. The README lists runtime behavioral bugs (logic, concurrency, error handling) as well as security scanning.
Q: Can it run without Node? A: The README notes Node.js 18+ is recommended; use the method that matches your environment.
Q: How do I reduce risk with auto-fix? A: Start with scan-only/plan-only/dry-run modes and require approvals before applying patches.