updated 2026-10-09 08:15 UTC

DeepEval

Repository Website

The LLM Evaluation Framework

Observability & Evaluation Python Listed Apache-2.0

Is DeepEval safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 13%
Last push 2d ago
Advisories None known
Compare DeepEval

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

Pick any agent to compare →
Suggest a correction

In detail: DeepEval scores 69.4/100 (Grade B), ranked #353 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.7/10; 13% of recent commits are signed; no published advisory affects its latest release (deepeval); last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships DeepEval 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.

  1. Source Partly signed

    github.com/confident-ai/deepeval, Apache-2.0, last pushed 2026-10-07. 13% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Oct 1, 2026). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 1
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • PyPI deepeval Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: deepeval 4.2.8. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of DeepEval.

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

Signed credential (JSON) How to verify

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 DeepEval compares in Observability & Evaluation

  1. #8 Opik 78.6 +9.2
  2. #9 Arize Phoenix 76.0 +6.6
  3. #10 DeepEval 69.4 this agent
  4. #11 Agenta 68.2 −1.2
  5. #12 Giskard 67.4 −2.0

Bars show each HVTrust score; the tick marks DeepEval’s 69.4.

Where the 69.4 comes from

HVTrust dimensions vs the Observability & Evaluation average

69.4 / 100 · 100.0% confidence

DeepEval Observability & Evaluation average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.3 / 25
5.4 below avg 10.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.2 below avg 13.0
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 11.3
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
6.0 above avg 13.9
AdoptionLog-scaled stars · package downloads
18.1 / 20
5.6 above avg 12.5

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 212 spots (#128 → #340)
2026-09-21
Rank Moved
Rank rose 209 spots (#335 → #126)
2026-09-11
Rank Moved
Rank dropped 11 spots (#323 → #334)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for DeepEval View Observability & Evaluation Report missing data
90.9
Activity sub-score · out of 100
#10
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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
18.7k
Forks
2.0k
Last Push
2026-10-07
2 days ago
Commits (4 wk)
124
Downloads (7d)
735,637
pypi
HN mentions (30d)
1
Open Issues
322
Rank Change
▼1
was #352

Analysis

Activity Inputs

90.9 / 100
StarsRepository reach
25.6 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.4 / 20

Common questions about DeepEval

DeepEval 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 DeepEval publish package provenance?
No published build provenance is currently detected for DeepEval. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepEval have an OpenSSF Scorecard?
DeepEval has an OpenSSF Scorecard score of 3.7/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 DeepEval actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does DeepEval use?
DeepEval ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepEval's commits signed?
13% of the last 100 commits to DeepEval 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
medium confidence
Implemented
DeepEval appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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

Maintain DeepEval?

For maintainers

HVTrust scores DeepEval 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
Rank 18
2026-09-23
Rank Moved
Rank dropped 212 spots (#128 → #340)
2026-09-21
Rank Moved
Rank rose 209 spots (#335 → #126)
2026-09-11
Rank Moved
Rank dropped 11 spots (#323 → #334)
2026-09-07
Rank Moved
Rank dropped 16 spots (#299 → #315)
2026-09-05
Rank Moved
Rank dropped 59 spots (#237 → #296)
2026-09-04
Rank Moved
Rank dropped 18 spots (#219 → #237)
2026-09-03
Rank Moved
Rank dropped 11 spots (#208 → #219)
2026-09-02
Rank Moved
Rank dropped 17 spots (#191 → #208)
2026-08-31
Rank Moved
Rank dropped 23 spots (#166 → #189)
2026-08-29
Rank Moved
Rank dropped 12 spots (#161 → #173)
2026-08-26
Rank Moved
Rank dropped 13 spots (#138 → #151)
2026-08-22
Rank Moved
Rank rose 12 spots (#141 → #129)
2026-08-19
Rank Moved
Rank dropped 10 spots (#130 → #140)
2026-08-17
Rank Moved
Rank rose 12 spots (#142 → #130)
2026-08-12
Rank Moved
Rank rose 10 spots (#136 → #126)
2026-08-10
Rank Moved
Rank dropped 14 spots (#123 → #137)
2026-08-08
Rank Moved
Rank dropped 12 spots (#110 → #122)
2026-07-13
Rank Moved
Rank dropped 13 spots (#87 → #100)
GitHub → Website → PyPI: deepeval

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 69.4 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/deepeval.svg)](https://hvtracker.net/agents/deepeval)
HTML:
<a href="https://hvtracker.net/agents/deepeval"><img src="https://hvtracker.net/badge/deepeval.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.4 · Raw JSON