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
Compare → Suggest correction
Listing state
Listed
HVTrust
71.6/100 · Grade B
Evidence coverage
Grade A · 4/5 signals
Last push
2026-05-02 · 78d ago
Recent change
Rank

Is Evidently safe? Evidently scores 71.6/100 (Grade B), ranked #93 of 418 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.5/10; 90% of recent commits are signed; last pushed 2026-05-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Quick Trust Read

Verdict
Promising trust profile, but some evidence still deserves review.
71.6/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Maintenance
6.8/20
What Would Improve It
Improve maintenance to lift the weakest part of the trust profile.
Recent Changes
2026-07-13
Rank Moved
Rank dropped 12 spots (#69 → #81)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Refresh maintenance signals The repo was last pushed 78 days ago. Fresh activity helps separate stable projects from stale ones.
51.3
Activity Score · out of 100
71.6
HVTrust Score · out of 100
#93
Global Rank · of 418
#6

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 →

Signals refreshed 2026-07-19 08:02 UTC · Repo last pushed 78 days ago

Rank Trend

2026-07-05 2026-07-19

Activity & Reach

Stars
7.7k
Forks
878
Last Push
2026-05-02
78 days ago
Commits (4 wk)
0
Downloads (7d)
296,228
pypi
HN mentions (30d)
6
Open Issues
234
Rank Change
▼1
was #92

Analysis

HVTrust Dimensions

71.6 / 100 · 100.0% confidence
Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.4 / 25
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
Maintenance60% last-push freshness · 40% commit activity
6.8 / 20
Adoption60% stars · 40% downloads, log-scaled
16.6 / 20

Activity Inputs

51.3 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
14.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.7 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Jul 18, 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 4
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Evidently safe?

Evidently has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
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.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 Evidently actively maintained?
Slowing down. Last push was 78 days ago — keep an eye on whether activity resumes.
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.

Ranked neighbours in Observability & Evaluation

AI agent 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
2 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
4 tags
Broad capability areas detected.
  • browser
  • code
  • database
  • search
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-06-05
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, Postgres

Maintain Evidently?

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.

Reputation Timeline

Listed 1Surface 1Rank 1
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

Embed Badge Badge guide for maintainers →

HVTrust 71.6 Grade B
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