Is AgentOps safe?
AgentOps scores 61.5/100 (Grade C), ranked #152 of 328 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 3.5/10;
100% of recent commits are signed;
last pushed 2026-06-25. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
61.5/100 · Grade C
Strongest Signal
Adoption
15.5/20
Weakest Signal
Safety / Integrity
9.4/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-04
Provider Removed
Runtime surface shrank — no longer detected: E2B
2026-06-25
Activity Resumed
Activity resumed
2026-06-25
Rank Moved
Rank rose 41 spots (#221 → #180)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed 16 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
5.7k
Forks
604
Last Push
2026-06-25
16 days ago
Commits (4 wk)
1
Downloads (7d)
70,168
pypi
HN mentions (30d)
48
Open Issues
112
Rank Change
=
was #152
Analysis
HVTrust Dimensions
61.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.4 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.5 / 17
MaintenanceFreshness and commits
12.1 / 20
AdoptionStars and downloads
15.5 / 20
Activity Inputs
62.1 / 100
StarsRepository reach
22.5 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
12.9 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Jun 22, 2026 (refresh pending)
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests1
CII-Best-Practices0
Code-Review1
Contributors10
Dangerous-Workflow-1
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies-1
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions-1
Vulnerabilities10
Is AgentOps safe?
AgentOps 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 AgentOps publish package provenance?
No published build provenance is currently detected for AgentOps. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AgentOps have an OpenSSF Scorecard?
AgentOps has an OpenSSF Scorecard score of 3.5/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 AgentOps actively maintained?
Maintained. Last push was 16 days ago.
What license does AgentOps use?
AgentOps ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AgentOps's commits signed?
100% of the last 100 commits to AgentOps 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.
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 Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to AgentOps'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.
Detected MCP server support changed: none → declared
Maintain AgentOps?
HVTrust scores AgentOps 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.
