Is DvalinCode safe to use?

DvalinCode has an HVTrust score of 84.3/100 (Grade A), ranked #54 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for DvalinCode?

DvalinCode scores 84.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 111 GitHub stars and is categorized under Security & Guardrails.

DvalinCode

arthurpanhku/dvalincode

Approvable, local-first AI coding agent for regulated teams: policy controls, governed MCP, evidence packs, audit trails

Security & Guardrails TypeScript Grade A Listed MIT

84.3/100

Rank #54 of 1283

Compare DvalinCode

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 1d ago

Recent change

New

Is DvalinCode safe? DvalinCode scores 84.3/100 (Grade A), ranked #54 of 1283 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 5.8/10; 96% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#2 Guardrails AI — 81.8 (A) → #3 NeMo Guardrails — 72.0 (B) → #4 REA — 70.5 (B) → #5 Snyk Agent Scan — 64.0 (C) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-08-10

Newly Listed

First tracked at rank #51

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.

Compare with Guardrails AI Get email alerts for DvalinCode View Security & Guardrails Report missing data

64.9

Activity sub-score · out of 100

In Security & Guardrails

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

2026-08-11 2026-08-12

Activity & Reach

Stars

111

Forks

Last Push

2026-08-11

yesterday

Commits (4 wk)

Downloads (7d)

582

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #52

Analysis

HVTrust Dimensions vs Security & Guardrails

84.3 / 100 · 100.0% confidence

DvalinCode Security & Guardrails average (19 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

19.6 / 25

11.3 above avg 8.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.1 above avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

1.7 above avg 11.7

Maintenance60% last-push freshness · 40% commit activity

19.3 / 20

3.0 above avg 16.3

AdoptionLog-scaled stars · package downloads

8.6 / 20

1.4 below avg 10.0

Activity Inputs

64.9 / 100

StarsRepository reach

12.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

22.9 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

96%

of last 100 commits verified

Dependency-Update-Tool 10

Code-Review 0

Dangerous-Workflow 10

Maintained 0

Security-Policy 10

Binary-Artifacts 10

Token-Permissions 10

Pinned-Dependencies 9

CII-Best-Practices 0

SAST 9

Vulnerabilities 0

License 10

Signed-Releases 0

Fuzzing 0

Branch-Protection -1

Packaging 10

Contributors 3

CI-Tests 9

Is DvalinCode safe?

Public supply-chain signals for DvalinCode are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but DvalinCode carries less obvious unverified-evidence risk than projects with thin signals.

Does DvalinCode publish package provenance?

Yes. DvalinCode's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does DvalinCode have an OpenSSF Scorecard?

DvalinCode has an OpenSSF Scorecard score of 5.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is DvalinCode actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does DvalinCode use?

DvalinCode ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are DvalinCode's commits signed?

96% of the last 100 commits to DvalinCode are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

DvalinCode vs Guardrails AI → DvalinCode vs NeMo Guardrails → DvalinCode vs REA →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

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 Server Support

high confidence

Implemented

DvalinCode appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Newly Listed

First tracked at rank #51

GitHub → npm: dvalincode

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/dvalincode.svg)](https://hvtracker.net/agents/dvalincode)
            
HTML:
            <a href="https://hvtracker.net/agents/dvalincode"><img src="https://hvtracker.net/badge/dvalincode.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

Data sources
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