DvalinCode vs Snyk Agent Scan
DvalinCode leads on trust: 83.9/100 (Grade A) against 63.5/100 (Grade C), a 20.4-point gap. DvalinCode leads on supply-chain integrity and provenance, and rests on broader evidence; Snyk Agent Scan leads on adoption.
Independent security verification for code written by humans and AI agents. Scan, repair, then prove it — Dvalin runs your project's own checks and issues a Verified Fix Record anyone can re-derive offline. Local-first, policy-bound, MIT.
Choose DvalinCode if supply-chain integrity and provenance matter most.
- +7.9Safety / Integrity: OSSF Scorecard 6.6 against 5.7
- +7.2Identity / Provenance: package provenance attested, against none
- +1.6Maintenance
- +0.8Transparency: OSSF Scorecard 6.6 against 5.7
Security scanner for AI agents, MCP servers and agent skills.
Choose Snyk Agent Scan if adoption matters most.
- +0.8Adoption: 3.1k GitHub stars against 118
Where they differ
An independent, evidence-based trust comparison of DvalinCode and Snyk Agent Scan, two Security & Guardrails projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.
Full evidence
| Signal | DvalinCodearthurpanhku/dvalincode | Snyk Agent Scansnyk/agent-scan |
|---|---|---|
| HVTrust score | 83.9 | 63.5 |
| Evidence grade | A | C |
| Coverage grade | B | C |
| Overall rank | #98 | #525 |
| Rank in Security & Guardrails | #2 | #6 |
| GitHub stars | 118 | 3.1k |
| Last updated | 4d ago | 1d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 6.6 / 10 | 5.7 / 10 |
| License | MIT | Apache-2.0 |
| Downloads | 91/wk | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 20.0 | 12.1 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.1 | 13.3 |
| Maintenance / 20 | 19.5 | 17.9 |
| Adoption / 20 | 7.6 | 8.4 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | 1 — Anthropic | 1 — Anthropic |
| Requires API keys | Yes | Yes |
| Plugin surface | plugins | — |
| Provenance drift | Match | — |
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →