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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 2 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
17.1k
Forks
1.9k
Last Push
2026-06-02
2 days ago
Commits (4 wk)
35
Downloads (7d)
20,131
pypi
HN mentions (30d)
0
Open Issues
452
Rank Change
▼5
was #58
Analysis
HVTrust Dimensions
70.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.4 / 17
MaintenanceFreshness and commits
18.1 / 20
AdoptionStars and downloads
15.9 / 20
Activity Inputs
84.8 / 100
StarsRepository reach
25.4 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
19.4 / 25
CommunityFork signal
15.3 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.9 / 10
via deps.dev · OpenSSF
Signed Commits
57%
of last 100 commits verified
Security-Policy10
Code-Review4
Maintained10
Dangerous-Workflow10
Token-Permissions9
Binary-Artifacts10
CII-Best-Practices0
Vulnerabilities0
SAST10
Pinned-Dependencies5
Branch-Protection-1
Fuzzing0
Dependency-Update-Tool10
License10
Packaging10
Signed-Releases0
CI-Tests10
Contributors10
Is CAMEL safe?
CAMEL has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does CAMEL publish package provenance?
No published build provenance is currently detected for CAMEL. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does CAMEL have an OpenSSF Scorecard?
CAMEL has an OpenSSF Scorecard score of 6.9/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 CAMEL actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does CAMEL use?
CAMEL ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are CAMEL's commits signed?
56% of the last 100 commits to CAMEL 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.
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain CAMEL?
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.
