AiSOC vs DvalinCode
Both are Grade A and 1.6 points apart, so choose on what you weigh most. AiSOC leads on maintenance and adoption; DvalinCode leads on supply-chain integrity and transparency.
Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Choose AiSOC if maintenance and adoption matter most.
- +3.9Adoption: 316 weekly downloads against 77
- +0.8Maintenance
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 transparency matter most.
- +2.4Safety / Integrity: 89% of recent commits signed, against 63%
- +0.6Transparency: OSSF Scorecard 6.4 against 5.6
Where they differ
1 dimension identical: Identity 18.0 · Full evidence table
An independent, evidence-based trust comparison of AiSOC and DvalinCode, 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 | AiSOCbeenuar/AiSOC | DvalinCodearthurpanhku/dvalincode |
|---|---|---|
| HVTrust score | 84.9 | 83.3 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #93 | #112 |
| Rank in Security & Guardrails | #3 | #4 |
| GitHub stars | 2.4k | 120 |
| Last updated | today | today |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.6 / 10 | 6.4 / 10 |
| License | MIT | MIT |
| Downloads | 316/wk | 77/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 17.6 | 20.0 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.3 | 13.9 |
| Maintenance / 20 | 20.0 | 19.2 |
| Adoption / 20 | 11.4 | 7.5 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | 1 — Anthropic |
| Requires API keys | Yes | Yes |
| Plugin surface | plugins | plugins |
| Provenance drift | Match | 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.4 →