DvalinCode
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.
Is DvalinCode safe? Strong public trust posture, backed by multiple independent signals.
Compare DvalinCode
How does it stack up against its Security & Guardrails neighbours?
Pick any agent to compare →In detail: DvalinCode scores 83.9/100 (Grade A), ranked #98 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 85% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How DvalinCode compares in Security & Guardrails
- #1 HOL Guard 91.9 +8.0
- #2 DvalinCode 83.9 this agent
- #3 Guardrails AI 76.7 −7.2
- #4 REA 73.8 −10.1
- #5 NeMo Guardrails 72.1 −11.8
Bars show each HVTrust score; the tick marks DvalinCode’s 83.9.
Where the 83.9 comes from
HVTrust dimensions vs the Security & Guardrails average
83.9 / 100 · 100.0% confidenceDvalinCode Security & Guardrails average (22 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
66.5 / 100Supply Chain Trust
Common questions about DvalinCode
Does DvalinCode publish package provenance?
Does DvalinCode have an OpenSSF Scorecard?
Is DvalinCode actively maintained?
What license does DvalinCode use?
Are DvalinCode's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare DvalinCode head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to DvalinCode's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain DvalinCode?
For maintainers
HVTrust scores DvalinCode from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/dvalincode)
<a href="https://hvtracker.net/agents/dvalincode"><img src="https://hvtracker.net/badge/dvalincode.svg" alt="HVTrust"></a>
Other agents in Security & Guardrails
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON