Is Evidently safe to use?

Evidently has an HVTrust score of 76.8/100 (Grade B), ranked #75 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Evidently?

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

Evidently

evidentlyai/evidently

Evidently is an open-source ML and LLM observability framework. Evaluate, test, and monitor any AI-powered system or d

Observability & Evaluation Jupyter Notebook Grade B Listed Apache-2.0

76.8/100

Rank #75 of 1204

Compare Evidently

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 A · 4/5 signals

Last push

2026-08-05 · 4d ago

Recent change

Provider Added +4

Is Evidently safe? Evidently scores 76.8/100 (Grade B), ranked #75 of 1204 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; OSSF Scorecard rates its supply-chain practices 3.3/10; 90% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Observability & Evaluation

#3 OpenLLMetry — 84.7 (A) → #4 Langfuse — 78.2 (B) → #6 LangWatch — 75.7 (B) → #7 Promptfoo — 75.3 (B) →

Quick Trust Read

What Would Improve It

Improve maintenance to lift the weakest part of the trust profile.

Recent Changes

2026-08-07

Provider Added

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

2026-08-05

Activity Resumed

Activity resumed

2026-08-05

Rank Moved

Rank rose 36 spots (#107 → #71)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with MLflow Get email alerts for Evidently View Observability & Evaluation Report missing data

61.5

Activity sub-score · out of 100

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

Activity & Reach

Stars

7.8k

Forks

896

Last Push

2026-08-05

4 days ago

Commits (4 wk)

Downloads (7d)

329,507

pypi

HN mentions (30d)

Open Issues

238

Rank Change

▲1

was #76

Analysis

HVTrust Dimensions vs Observability & Evaluation

76.8 / 100 · 100.0% confidence

Evidently Observability & Evaluation average (22 agents)

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

16.1 / 25

5.3 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.9 above avg 13.1

Transparency50% declared license · 50% OSSF Scorecard

11.3 / 17

in line with avg 11.7

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

3.7 below avg 15.4

AdoptionLog-scaled stars · package downloads

16.7 / 20

2.4 above avg 14.3

Activity Inputs

61.5 / 100

StarsRepository reach

23.4 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

3.3 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

90%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Evidently safe?

Public supply-chain signals for Evidently are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Evidently carries less obvious unverified-evidence risk than projects with thin signals.

Does Evidently publish package provenance?

Yes. Evidently's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Evidently have an OpenSSF Scorecard?

Evidently has an OpenSSF Scorecard score of 3.3/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 Evidently actively maintained?

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

What license does Evidently use?

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

Are Evidently's commits signed?

90% of the last 100 commits to Evidently 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 Evidently head-to-head

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

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

3 detected

Public provider/service dependencies detected.

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

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

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

How this surface has changed

Detected changes to Evidently'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

Provider Added

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

2026-08-05

Activity Resumed

Activity resumed

2026-07-31

Activity Went Stale

No commits for 90 days

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: OpenAI, Postgres

Maintain Evidently?

For maintainers

HVTrust scores Evidently 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-07

Provider Added

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

2026-08-05

Activity Resumed

Activity resumed

2026-08-05

Rank Moved

Rank rose 36 spots (#107 → #71)

2026-08-05

HVTrust Changed

HVTrust up 6.3pts (70.0 → 76.3)

2026-08-05

Activity Score Changed

Activity score up 13pts (49 → 62)

2026-07-31

Activity Went Stale

No commits for 90 days

2026-07-13

Rank Moved

Rank dropped 12 spots (#69 → #81)

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependencies: OpenAI, Postgres

2026-06-02

Newly Listed

First tracked at rank #41

GitHub → PyPI: evidently

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/evidently.svg)](https://hvtracker.net/agents/evidently)
            
HTML:
            <a href="https://hvtracker.net/agents/evidently"><img src="https://hvtracker.net/badge/evidently.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON