CAMEL
Website
🐫 CAMEL: The first and the best multi-agent framework. Finding the Scaling Law of Agents. https://www.camel-ai.org
Is CAMEL safe? Promising trust profile, but some evidence still deserves review.
Compare CAMEL
How does it stack up against its Multi-Agent Systems neighbours?
Pick any agent to compare →In detail: CAMEL scores 64.0/100 (Grade C), ranked #526 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.8/10; 56% of recent commits are signed; no published advisory affects its latest release (camel-ai); last pushed 2026-10-05. Every point is earned from checkable signals — never paid placement. How scoring works →
How CAMEL 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.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 78.7 B · #2 of 43
- Raise the OSSF Scorecard from 6.8 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Signed-Releases 0 +4.6 → 68.6 B · #4 of 43
- Sign every commit56% signed today +2.2 → 66.2 B · #6 of 43
Chain of custody
Scanners check what the code says. This traces who ships CAMEL and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/camel-ai/camel, Apache-2.0, last pushed 2026-10-05. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 6.8/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protectionn/a
- Signed Releases0
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies5
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection -1CI-Tests 10CII-Best-Practices 0Code-Review 3Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 5SAST 10Security-Policy 10Signed-Releases 0Token-Permissions 9Vulnerabilities 0 -
Published packages Linked, not attested
- PyPI camel-ai Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: camel-ai 0.2.90. No published advisory affects it (OSV, checked 2026-10-09).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of CAMEL.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues CAMEL’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 CAMEL compares in Multi-Agent Systems
- #10 OpenExecutive 64.9 +0.9
- #11 Rakazo 64.1 +0.1
- #12 CAMEL 64.0 this agent
- #13 Agency Agents 63.3 −0.7
- #14 Octop 63.2 −0.8
Bars show each HVTrust score; the tick marks CAMEL’s 64.0.
Where the 64.0 comes from
HVTrust dimensions vs the Multi-Agent Systems average
64.0 / 100 · 100.0% confidenceCAMEL Multi-Agent Systems average (43 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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
73.1 / 100Common questions about CAMEL
Does CAMEL publish package provenance?
Does CAMEL have an OpenSSF Scorecard?
Is CAMEL actively maintained?
What license does CAMEL use?
Are CAMEL'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 →
- Amazon Bedrock
- Anthropic
- Cohere
- E2B
- Firecrawl
- Google Gemini
- Mistral AI
- Multi-provider (LiteLLM)
- OpenAI
- Postgres
- Qdrant
- Redis
- Tavily
- Weaviate
- browser
- database
- search
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to CAMEL'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 CAMEL?
For maintainers
HVTrust scores CAMEL 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/camel)
<a href="https://hvtracker.net/agents/camel"><img src="https://hvtracker.net/badge/camel.svg" alt="HVTrust"></a>
Other agents in Multi-Agent Systems
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON