Is OpenLLMetry safe?
OpenLLMetry scores 55.0/100 (Grade C), ranked #231 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
OSSF Scorecard rates its supply-chain practices 6.7/10;
81% of recent commits are signed;
last pushed 2026-07-10. 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.
55.0/100 · Grade C
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Adoption
9.3/20
What Would Improve It
Expose more independent signals, such as package metadata, provenance, or public usage evidence.
Recent Changes
2026-07-13
Newly Listed
First tracked at rank #231
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.
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 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 →
Signals refreshed2026-07-13 10:01 UTC·Repo last pushed 3 days ago
Activity & Reach
Stars
7.3k
Forks
1.0k
Last Push
2026-07-10
3 days ago
Commits (4 wk)
14
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
107
Rank Change
NEW
Analysis
HVTrust Dimensions
55.0 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
19.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
14.2 / 17
MaintenanceFreshness and commits
16.5 / 20
AdoptionStars and downloads
9.3 / 20
Activity Inputs
76.6 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
14.7 / 25
CommunityFork signal
14.0 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.7 / 10
OpenSSF Scorecard · scanned Jul 13, 2026
Signed Commits
81%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection5
CI-Tests10
CII-Best-Practices0
Code-Review9
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies2
SAST10
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is OpenLLMetry safe?
OpenLLMetry 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 OpenLLMetry publish package provenance?
Yes. OpenLLMetry's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does OpenLLMetry have an OpenSSF Scorecard?
OpenLLMetry has an OpenSSF Scorecard score of 6.7/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 OpenLLMetry actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does OpenLLMetry use?
OpenLLMetry ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenLLMetry's commits signed?
81% of the last 100 commits to OpenLLMetry 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
high confidence
Implemented
OpenLLMetry appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
database
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
Maintain OpenLLMetry?
HVTrust scores OpenLLMetry 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.
