Is Deep Agents safe to use?

Deep Agents has an HVTrust score of 76.0/100 (Grade B), ranked #235 of 1378 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Deep Agents?

Deep Agents scores 76.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 30.5k GitHub stars and is categorized under Agent Frameworks.

Deep Agents

Repository

Website by langchain-ai

The batteries-included agent harness.

Agent Frameworks Python Listed MIT

Is Deep Agents safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.0 / 10

Provenance None

Signed commits 100%

Last push today

Advisories None known

Compare Deep Agents

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Deep Agents scores 76.0/100 (Grade B), ranked #235 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; no published advisory affects its latest release (deepagents); last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Deep Agents 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.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +12.2 → 88.2 A · #9 of 130
Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +7.6 → 83.6 A · #12 of 130

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Signed

github.com/langchain-ai/deepagents, MIT, last pushed 2026-10-21. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Oct 20, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection4
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies5
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 3

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 4

Security-Policy 9

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5
Published packages Linked, not attested
- PyPI deepagents Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: deepagents 0.7.28. No published advisory affects it (OSV, checked 2026-10-21).

Changes to this chain

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

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Deep Agents’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 Deep Agents compares in Agent Frameworks

Bars show each HVTrust score; the tick marks Deep Agents’s 76.0.

Where the 76.0 comes from

HVTrust dimensions vs the Agent Frameworks average

76.0 / 100 · 100.0% confidence

Deep Agents Agent Frameworks average (130 agents)

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

11.2 / 25

1.2 above avg 10.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

in line with avg 12.5

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.3 above avg 14.7

AdoptionLog-scaled stars · package downloads

19.1 / 20

7.9 above avg 11.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-20

Rank Moved

Rank dropped 13 spots (#221 → #234)

2026-10-09

Rank Moved

Rank dropped 11 spots (#208 → #219)

2026-09-28

Rank Moved

Rank rose 14 spots (#213 → #199)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.0/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.

Compare with another agent Get email alerts for Deep Agents View Agent Frameworks Report missing data

93.8

Activity sub-score · out of 100

#19

In Agent Frameworks

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

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars

30.5k

Forks

4.3k

Last Push

2026-10-21

today

Commits (4 wk)

449

Downloads (7d)

1,843,278

pypi

HN mentions (30d)

—

Open Issues

163

Rank Change

▼1

was #234

Analysis

Activity Inputs

93.8 / 100

StarsRepository reach

26.9 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.9 / 20

Common questions about Deep Agents

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

Does Deep Agents publish package provenance?

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

Does Deep Agents have an OpenSSF Scorecard?

Deep Agents has an OpenSSF Scorecard score of 5.0/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 Deep Agents actively maintained?

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

What license does Deep Agents use?

Deep Agents ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Deep Agents's commits signed?

100% of the last 100 commits to Deep Agents 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

Deep Agents appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

12 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

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 Deep Agents'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-09-08

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-02

Tool Surface Changed

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

Maintain Deep Agents?

For maintainers

HVTrust scores Deep Agents 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-10-20

Rank Moved

Rank dropped 13 spots (#221 → #234)

2026-10-09

Rank Moved

Rank dropped 11 spots (#208 → #219)

2026-09-28

Rank Moved

Rank rose 14 spots (#213 → #199)

2026-09-23

Rank Moved

Rank dropped 123 spots (#84 → #207)

2026-09-21

Rank Moved

Rank rose 114 spots (#196 → #82)

2026-09-08

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-07

Rank Moved

Rank dropped 11 spots (#168 → #179)

2026-09-06

Rank Moved

Rank rose 12 spots (#180 → #168)

2026-09-05

Rank Moved

Rank dropped 39 spots (#141 → #180)

2026-09-02

Tool Surface Changed

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

2026-09-02

Rank Moved

Rank dropped 21 spots (#114 → #135)

2026-08-31

Rank Moved

Rank dropped 13 spots (#97 → #110)

2026-08-26

Rank Moved

Rank dropped 10 spots (#79 → #89)

GitHub → Website → PyPI: deepagents

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Deep Agents

How Deep Agents could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Deep Agents compares in Agent Frameworks

Where the 76.0 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Deep Agents

AI agent surface

Maintain Deep Agents?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks