DvalinCode vs NeMo Guardrails
DvalinCode leads on trust: 83.9/100 (Grade A) against 72.1/100 (Grade B), a 11.8-point gap. DvalinCode leads on provenance and supply-chain integrity; NeMo Guardrails leads on adoption and rests on broader evidence. Note: DvalinCode's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.
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 provenance and supply-chain integrity matter most.
- +7.2Identity / Provenance: package provenance attested, against none
- +6.1Safety / Integrity: package provenance attested, against none
- +2.5Maintenance
NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLM-based conversational systems.
Choose NeMo Guardrails if adoption matters most.
- +8.3Adoption: 88.9k weekly downloads against 91
- A vs BEvidence coverage: 4 of 5 independent signal types, against 3
Where they differ
An independent, evidence-based trust comparison of DvalinCode and NeMo Guardrails, 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 | NeMo GuardrailsNVIDIA/NeMo-Guardrails |
|---|---|---|
| HVTrust score | 83.9 | 72.1 |
| Evidence grade | A | B |
| Coverage grade | B | A |
| Overall rank | #98 | #289 |
| Rank in Security & Guardrails | #2 | #5 |
| GitHub stars | 118 | 7.2k |
| Last updated | 4d ago | today |
| Build provenance | Yes | No |
| OSSF Scorecard | 6.6 / 10 | 7.1 / 10 |
| License | MIT | NOASSERTION |
| Downloads | 91/wk | 89k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 20.0 | 13.9 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 14.1 | 14.5 |
| Maintenance / 20 | 19.5 | 17.0 |
| Adoption / 20 | 7.6 | 15.9 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | — |
| External providers | 1 — Anthropic | 1 — OpenAI |
| Requires API keys | Yes | No |
| Plugin surface | plugins | — |
| Provenance drift | Match | Unknown |
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 →