ACI.dev
Website
ACI.dev is the open source tool-calling platform that hooks up 600+ tools into any agentic IDE or custom AI agent through direct function calling or a unified MCP server. The birthplace of VibeOps.
Is ACI.dev safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare ACI.dev
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: ACI.dev scores 43.4/100 (Grade D), ranked #1139 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 93% of recent commits are signed; last pushed 2026-05-28. Every point is earned from checkable signals — never paid placement. How scoring works →
How ACI.dev could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +10.2 → 53.6 C · #45 of 62
Chain of custody
Scanners check what the code says. This traces who ships ACI.dev and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/aipotheosis-labs/aci, Apache-2.0, last pushed 2026-05-28. 93% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection5
- Signed Releasesn/a
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 5CI-Tests 8CII-Best-Practices 0Code-Review 3Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 1SAST 9Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. ACI.dev is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of ACI.dev.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues ACI.dev’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How ACI.dev compares in Protocols & Tool Integration
- #52 Klavis AI 44.2 +0.8
- #53 MCPJungle 43.7 +0.3
- #54 ACI.dev 43.4 this agent
- #55 MetaMCP 42.7 −0.7
- #56 mcpo 40.6 −2.8
Bars show each HVTrust score; the tick marks ACI.dev’s 43.4.
Where the 43.4 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
43.4 / 100 · 100.0% confidenceACI.dev Protocols & Tool Integration average (62 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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
40.6 / 100Common questions about ACI.dev
Does ACI.dev publish package provenance?
Does ACI.dev have an OpenSSF Scorecard?
Is ACI.dev actively maintained?
What license does ACI.dev use?
Are ACI.dev'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 →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to ACI.dev'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 ACI.dev?
For maintainers
HVTrust scores ACI.dev 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/aci-dev)
<a href="https://hvtracker.net/agents/aci-dev"><img src="https://hvtracker.net/badge/aci-dev.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON