Security review vs Spec to code compliance
Security review is an open-source agent skill for security. Spec to code compliance is an open-source agent skill for security.
- Security review has more GitHub stars (41,254 vs 8,243).
- Security review is best for check my repository for sql injection or xss before a release.
- Spec to code compliance is best for check a smart contract against its published whitepaper.
- What it is
- Security review is an open-source agent skill for security.Spec to code compliance is an open-source agent skill for security.
- Best for
- Check my repository for SQL injection or XSS before a releaseCheck a smart contract against its published whitepaper
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code
- GitHub stars
- 41.3K8.2K
- Last commit
- Nov 2026Nov 2026
- License
- MITCC-BY-SA-4.0
- Open source
- Good for
- Check my repository for SQL injection or XSS before a release; Scan the project for hardcoded API keys and credentials; Audit package.json and lock files for vulnerable dependenciesCheck a smart contract against its published whitepaper; Find requirements in a protocol spec that the implementation does not enforce; Compare a service's design document with the code behind it
What Security review does
Dependency vulnerability audit
Checks manifests and lock files across npm, Python, Java, Ruby, Rust and Go against a CVE watchlist.
Secrets exposure scan
Looks for hardcoded keys, tokens, private keys, connection strings and committed env files, including CI and IaC files.
Injection flaw detection
Reasons about SQL, command, XSS and other injection paths by tracing user input to sinks.
Access control review
Examines authentication, authorization, JWT handling, CSRF and privilege escalation paths.
Cross-file data flow tracing
Follows input across modules and services to find issues that only appear when files are read together.
Severity-rated report
Produces findings with severity, confidence, file location and plain-English risk explanations.
What Spec to code compliance does
Requirement-by-requirement verdicts
Each requirement is classed as implemented, partial, contradicted, stronger than the spec, absent or undecidable.
Adversarial divergence checking
Reported divergences are re-examined by separate agents that did not produce them before being kept.
Reverse gap discovery
Finds behavior the code has that no document mentions, which requirement-driven checks would miss.
Evidence-backed absence findings
Absent verdicts record the patterns searched and their results so real gaps can be told apart from incomplete searches.
Severity guidance
A rubric ranks divergences by consequence and separates behavioral defects from documentation fixes.
Domain reference notes
Guidance on specifications and enforcement for contracts, C and C++, services, firmware and standards.
Security review vs Spec to code compliance: questions
Is Security review or Spec to code compliance cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Security review and Spec to code compliance?
Security review is an open-source agent skill for security. Spec to code compliance is an open-source agent skill for security. Security review has more GitHub stars (41,254 vs 8,243).

