updated 2026-08-19 05:32 UTC

OpenLLMetry

traceloop/openllmetry

Open-source observability for your GenAI or LLM application, based on OpenTelemetry

Observability & Evaluation Python Grade A Listed Apache-2.0
84.9/100
Rank #51 of 1308
Compare OpenLLMetry

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-10 · 9d ago
Recent change
No recent signal change

Is OpenLLMetry safe? OpenLLMetry scores 84.9/100 (Grade A), ranked #51 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 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-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#2 Promptfoo — 88.7 (A) → #3 Weights & Biases Weave — 86.5 (A) → #5 Langfuse — 78.1 (B) → #6 Arize Phoenix — 76.4 (B) →

Quick Trust Read

What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-08-09
Activity Score Changed
Activity score up 7pts (62 → 68)
2026-07-28
Grade Changed
Trust grade C → A
2026-07-28
Rank Moved
Rank rose 231 spots (#281 → #50)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/10. Tighten the weakest checks to improve public safety evidence.
Compare with MLflow Get email alerts for OpenLLMetry View Observability & Evaluation Report missing data
69.9
Activity sub-score · out of 100
#4
In Observability & Evaluation

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-19 05:32 UTC · Repo last pushed 9 days ago

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars
7.4k
Forks
1.1k
Last Push
2026-08-10
9 days ago
Commits (4 wk)
4
Downloads (7d)
527,043
pypi
HN mentions (30d)
—
Open Issues
116
Rank Change
▼4
was #47

Analysis

HVTrust Dimensions vs Observability & Evaluation

84.9 / 100 · 100.0% confidence

OpenLLMetry Observability & Evaluation average (23 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.9 / 25
8.9 above avg 11.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.0 above avg 13.0
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
2.3 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
14.2 / 20
0.9 below avg 15.1
AdoptionLog-scaled stars · package downloads
16.9 / 20
3.0 above avg 13.9

Activity Inputs

69.9 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
14.1 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.7 / 10
OpenSSF Scorecard · scanned Aug 18, 2026
Signed Commits
81%
of last 100 commits verified
Binary-Artifacts 9
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 8
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 2
SAST 10
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is OpenLLMetry safe?

Public supply-chain signals for OpenLLMetry are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but OpenLLMetry carries less obvious unverified-evidence risk than projects with thin signals.
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?
Maintained. Last push was 9 days ago.
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.

Compare OpenLLMetry head-to-head

OpenLLMetry vs MLflow → OpenLLMetry vs Promptfoo → OpenLLMetry vs Weights & Biases Weave →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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.
External Service Dependencies
high confidence
9 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas 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?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 3Score 2Listed 1HVTrust 1Grade 1
2026-08-09
Activity Score Changed
Activity score up 7pts (62 → 68)
2026-07-28
Grade Changed
Trust grade C → A
2026-07-28
Rank Moved
Rank rose 231 spots (#281 → #50)
2026-07-28
HVTrust Changed
HVTrust up 29.9pts (53.3 → 83.2)
2026-07-28
Activity Score Changed
Activity score down 9pts (69 → 60)
2026-07-15
Rank Moved
Rank dropped 13 spots (#251 → #264)
2026-07-14
Rank Moved
Rank dropped 16 spots (#235 → #251)
2026-07-13
Newly Listed
First tracked at rank #235
GitHub → PyPI: traceloop-sdk

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 84.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/openllmetry.svg)](https://hvtracker.net/agents/openllmetry)
HTML:
<a href="https://hvtracker.net/agents/openllmetry"><img src="https://hvtracker.net/badge/openllmetry.svg" alt="HVTrust"></a>

Other agents in Observability & Evaluation

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON