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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 33 days ago
Rank Trend
2026-06-022026-06-04
Activity & Reach
Stars
7.6k
Forks
858
Last Push
2026-05-02
33 days ago
Commits (4 wk)
0
Downloads (7d)
289,455
pypi
HN mentions (30d)
5
Open Issues
273
Rank Change
▼8
was #43
Analysis
HVTrust Dimensions
72.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
16.8 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
11.7 / 17
MaintenanceFreshness and commits
9.8 / 20
AdoptionStars and downloads
16.6 / 20
Activity Inputs
57.3 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
20.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.6 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
3.8 / 10
via deps.dev · OpenSSF
Signed Commits
90%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests9
CII-Best-Practices0
Code-Review3
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained8
Packaging10
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions0
Vulnerabilities0
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.8/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 33 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
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.
