Opik has an HVTrust score of 48.5/100 (Grade D), ranked #461 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Opik?

Opik scores 48.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 21.3k GitHub stars and is categorized under Observability & Evaluation.

Opik

comet-ml/opik

Debug, evaluate, and monitor your LLM applications, RAG systems, and agentic workflows with comprehensive tracing, autom

Observability & Evaluation Python Grade D Listed Apache-2.0

48.5/100

Rank #461 of 1204

Compare Opik

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +4

Is Opik safe? Opik scores 48.5/100 (Grade D), ranked #461 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 89% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#15 OpenLIT — 60.9 (C) → #16 AgentOps — 57.9 (C) → #18 Ragas — 45.6 (D) → #19 TruLens — 44.3 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 116 spots (#341 → #457)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Opik View Observability & Evaluation Report missing data

91.0

Activity sub-score · out of 100

#17

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 D 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 →

Activity & Reach

Stars

21.3k

Forks

1.7k

Last Push

2026-08-09

today

Commits (4 wk)

308

Downloads (7d)

936,642

npm+pypi

HN mentions (30d)

205

Open Issues

Rank Change

▼4

was #457

Analysis

HVTrust Dimensions vs Observability & Evaluation

48.5 / 100 · 75.0% confidence

Opik Observability & Evaluation average (22 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.5 / 25

6.3 below avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.3 below avg 13.1

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.2 below avg 11.7

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

4.6 above avg 15.4

AdoptionLog-scaled stars · package downloads

18.3 / 20

4.0 above avg 14.3

Activity Inputs

91.0 / 100

StarsRepository reach

26.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

15.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

89%

of last 100 commits verified

Is Opik safe?

Public trust evidence for Opik is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Opik publish package provenance?

No published build provenance is currently detected for Opik. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Opik have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Opik. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Opik actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Opik use?

Opik ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Opik's commits signed?

89% of the last 100 commits to Opik 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.

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

Opik appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

medium confidence

Partial

Some package metadata matches; some source metadata is missing

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

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-08-07

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-08

Rank Moved

Rank dropped 116 spots (#341 → #457)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: declared → extension-based

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Google Gemini

2026-08-07

Provider Added

Runtime surface grew — new detected provider dependency: Multi-provider (LiteLLM)

2026-08-07

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-07-29

Rank Moved

Rank dropped 10 spots (#330 → #340)

2026-07-15

Rank Moved

Rank dropped 23 spots (#302 → #325)

2026-07-14

Rank Moved

Rank dropped 17 spots (#285 → #302)

2026-07-13

Rank Moved

Rank dropped 34 spots (#251 → #285)

2026-06-24

Rank Moved

Rank dropped 32 spots (#219 → #251)

2026-06-23

Rank Moved

Rank dropped 13 spots (#206 → #219)

2026-06-18

Rank Moved

Rank dropped 13 spots (#168 → #181)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-06-03

Rank Moved

Rank rose 38 spots (#189 → #151)

2026-06-03

HVTrust Changed

HVTrust up 19.6pts (27.1 → 46.7)

2026-06-02

Newly Listed

First tracked at rank #189

GitHub → PyPI: opik npm: opik

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/opik.svg)](https://hvtracker.net/agents/opik)
            
HTML:
            <a href="https://hvtracker.net/agents/opik"><img src="https://hvtracker.net/badge/opik.svg" alt="HVTrust"></a>

Other agents in Observability & Evaluation

Data sources
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.2 · Raw JSON