updated 2026-10-11 16:06 UTC

OpenLLMetry

Repository Website

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

Observability & Evaluation Python Listed Apache-2.0

Is OpenLLMetry safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.5 / 10
Provenance Attested
Signed commits 82%
Last push today
Advisories None known
Compare OpenLLMetry

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

Pick any agent to compare →
Suggest a correction

In detail: OpenLLMetry scores 86.4/100 (Grade A), ranked #70 of 1371 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.5/10; 82% of recent commits are signed; no published advisory affects its latest release (traceloop-sdk); last pushed 2026-10-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenLLMetry 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenLLMetry 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.

  1. Source Signed

    github.com/traceloop/openllmetry, Apache-2.0, last pushed 2026-10-11. 82% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.5/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

    • Code Review8
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    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 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI traceloop-sdk Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: traceloop-sdk 0.62.4. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of OpenLLMetry.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues OpenLLMetry’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.

Signed credential (JSON) How to verify

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 OpenLLMetry compares in Observability & Evaluation

  1. #1 Promptfoo 92.6 +6.2
  2. #2 MLflow 89.6 +3.2
  3. #3 OpenLLMetry 86.4 this agent
  4. #4 Weights & Biases Weave 84.5 −1.9
  5. #5 LangWatch 83.1 −3.3

Bars show each HVTrust score; the tick marks OpenLLMetry’s 86.4.

Where the 86.4 comes from

HVTrust dimensions vs the Observability & Evaluation average

86.4 / 100 · 100.0% confidence

OpenLLMetry Observability & Evaluation average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.7 / 25
8.5 above avg 11.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
2.1 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
1.6 above avg 15.2
AdoptionLog-scaled stars · package downloads
16.8 / 20
3.4 above avg 13.4

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-10-06
Rank Moved
Rank rose 22 spots (#92 → #70)
2026-09-23
Rank Moved
Rank dropped 37 spots (#61 → #98)
2026-09-21
Rank Moved
Rank rose 38 spots (#99 → #61)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with Promptfoo Get email alerts for OpenLLMetry View Observability & Evaluation Report missing data
77.4
Activity sub-score · out of 100
#3
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-10-11 16:06 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
7.5k
Forks
1.1k
Last Push
2026-10-11
today
Commits (4 wk)
15
Downloads (7d)
444,039
pypi
HN mentions (30d)
—
Open Issues
150
Rank Change
▲3
was #73

Analysis

Activity Inputs

77.4 / 100
StarsRepository reach
23.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
15.0 / 25
CommunityFork signal
14.2 / 20

Common questions about OpenLLMetry

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.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 OpenLLMetry actively maintained?
Actively maintained. The repository was pushed to within the last 1 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?
82% 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 Promptfoo → OpenLLMetry vs MLflow → 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 10Score 4HVTrust 1Grade 1
2026-10-06
Rank Moved
Rank rose 22 spots (#92 → #70)
2026-09-23
Rank Moved
Rank dropped 37 spots (#61 → #98)
2026-09-21
Rank Moved
Rank rose 38 spots (#99 → #61)
2026-09-16
Rank Moved
Rank rose 34 spots (#132 → #98)
2026-09-16
Activity Score Changed
Activity score up 9pts (57 → 66)
2026-09-15
Rank Moved
Rank dropped 10 spots (#122 → #132)
2026-09-09
Rank Moved
Rank dropped 25 spots (#90 → #115)
2026-09-09
Activity Score Changed
Activity score down 6pts (64 → 58)
2026-09-05
Rank Moved
Rank dropped 16 spots (#63 → #79)
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)
GitHub → Website → PyPI: traceloop-sdk

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.4 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.4 · Raw JSON