Opik
Website
Debug, evaluate, and monitor your LLM applications, RAG systems, and agentic workflows with comprehensive tracing, automated evaluations, and production-ready dashboards.
Is Opik safe? Strong public trust posture, backed by multiple independent signals.
Compare Opik
How does it stack up against its Observability & Evaluation neighbours?
Pick any agent to compare →In detail: Opik scores 78.7/100 (Grade B), ranked #194 of 1378 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 93% of recent commits are signed; no published advisory affects its latest release (opik); last pushed 2026-10-17. Every point is earned from checkable signals — never paid placement. How scoring works →
How Opik 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.
- Raise the OSSF Scorecard to 9.0no OSSF Scorecard result yet +15.7 → 94.4 A · #1 of 27
Chain of custody
Scanners check what the code says. This traces who ships Opik 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.
-
Source Signed
github.com/comet-ml/opik, Apache-2.0, last pushed 2026-10-17. 93% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Not checked
No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.
-
What you install today No known advisories
Latest release checked: opik 2.2.102. No published advisory affects it (OSV, checked 2026-10-17).
Changes to this chain
- 2026-09-02 Package provenance attestation detected
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Opik’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.
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 Opik compares in Observability & Evaluation
- #5 Weights & Biases Weave 84.2 +5.5
- #6 Langfuse 79.1 +0.4
- #7 Opik 78.7 this agent
- #8 Arize Phoenix 76.9 −1.8
- #9 Latitude 76.8 −1.9
Bars show each HVTrust score; the tick marks Opik’s 78.7.
Where the 78.7 comes from
HVTrust dimensions vs the Observability & Evaluation average
78.7 / 100 · 100.0% confidenceOpik Observability & Evaluation average (27 agents)
Quick Trust Read
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. 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
91.3 / 100Common questions about Opik
Does Opik publish package provenance?
Does Opik have an OpenSSF Scorecard?
Is Opik actively maintained?
What license does Opik use?
Are Opik's commits signed?
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 Opik head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Opik'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.
Maintain Opik?
For maintainers
HVTrust scores Opik 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/opik)
<a href="https://hvtracker.net/agents/opik"><img src="https://hvtracker.net/badge/opik.svg" alt="HVTrust"></a>
Other agents in Observability & Evaluation
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON