Delimit — API Governance for AI Coding Assistants
The merge gate for AI-written code, with signed, replayable attestation. Works across Claude Code, Codex, Cursor, and Ge
Compare Delimit — API Governance for AI Coding Assistants
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →Promising trust profile, but some evidence still deserves review.
Is Delimit — API Governance for AI Coding Assistants safe? Delimit — API Governance for AI Coding Assistants scores 74.2/100 (Grade B), ranked #157 of 1320 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 4.6/10; 86% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in MCP Servers
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 B 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
HVTrust Dimensions vs MCP Servers
74.2 / 100 · 100.0% confidenceDelimit — API Governance for AI Coding Assistants MCP Servers average (778 agents)
Activity Inputs
48.3 / 100Supply Chain Trust
Is Delimit — API Governance for AI Coding Assistants safe?
Does Delimit — API Governance for AI Coding Assistants publish package provenance?
Does Delimit — API Governance for AI Coding Assistants have an OpenSSF Scorecard?
Is Delimit — API Governance for AI Coding Assistants actively maintained?
What license does Delimit — API Governance for AI Coding Assistants use?
Are Delimit — API Governance for AI Coding Assistants'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.
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
Maintain Delimit — API Governance for AI Coding Assistants?
For maintainers
HVTrust scores Delimit — API Governance for AI Coding Assistants 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/delimit-api-governance-for-ai-coding-assistants)
<a href="https://hvtracker.net/agents/delimit-api-governance-for-ai-coding-assistants"><img src="https://hvtracker.net/badge/delimit-api-governance-for-ai-coding-assistants.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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