Is Deepsec safe to use?

Deepsec has an HVTrust score of 59.9/100 (Grade C), ranked #316 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Deepsec?

Deepsec scores 59.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.6k GitHub stars and is categorized under Security & Guardrails.

Deepsec

vercel-labs/deepsec

Deepsec is a security harness for finding vulnerabilities in your codebase powered by coding agents

Security & Guardrails TypeScript Grade C Listed Apache-2.0

59.9/100

Rank #316 of 1283

Compare Deepsec

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-13 · 2d ago

Recent change

Rank +4

Is Deepsec safe? Deepsec scores 59.9/100 (Grade C), ranked #316 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.6/10; 100% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#5 PentAGI — 63.6 (C) → #6 SkillSpector — 63.0 (C) → #8 Garak — 58.9 (C) → #9 PentestAgent — 56.6 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-15

Rank Moved

Rank rose 16 spots (#332 → #316)

2026-08-13

Rank Moved

Rank dropped 16 spots (#316 → #332)

2026-08-12

Rank Moved

Rank rose 19 spots (#335 → #316)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/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 Guardrails AI Get email alerts for Deepsec View Security & Guardrails Report missing data

76.6

Activity sub-score · out of 100

In Security & Guardrails

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars

7.6k

Forks

459

Last Push

2026-08-13

2 days ago

Commits (4 wk)

19?

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲16

was #332

Analysis

HVTrust Dimensions vs Security & Guardrails

59.9 / 100 · 100.0% confidence

Deepsec Security & Guardrails average (19 agents)

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

12.0 / 25

3.6 above avg 8.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.1 below avg 11.9

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.6 above avg 11.7

Maintenance60% last-push freshness · 40% commit activity

14.5 / 20

1.7 below avg 16.2

AdoptionLog-scaled stars · package downloads

9.3 / 20

0.6 below avg 9.9

Activity Inputs

76.6 / 100

StarsRepository reach

23.3 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

16.2 / 25

CommunityFork signal

12.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.6 / 10

OpenSSF Scorecard · scanned Aug 14, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is Deepsec safe?

Deepsec 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 Deepsec publish package provenance?

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

Does Deepsec have an OpenSSF Scorecard?

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

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

What license does Deepsec use?

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

Are Deepsec's commits signed?

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

Deepsec vs Guardrails AI → Deepsec vs NeMo Guardrails → Deepsec vs REA →

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

None detected

No clear third-party provider dependency 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

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Deepsec?

For maintainers

HVTrust scores Deepsec 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-15

Rank Moved

Rank rose 16 spots (#332 → #316)

2026-08-13

Rank Moved

Rank dropped 16 spots (#316 → #332)

2026-08-12

Rank Moved

Rank rose 19 spots (#335 → #316)

2026-08-10

Rank Moved

Rank dropped 19 spots (#315 → #334)

2026-08-08

Rank Moved

Rank dropped 75 spots (#237 → #312)

2026-07-29

Rank Moved

Rank rose 15 spots (#260 → #245)

2026-07-23

Rank Moved

Rank dropped 12 spots (#245 → #257)

2026-07-22

Rank Moved

Rank dropped 16 spots (#229 → #245)

2026-07-18

Rank Moved

Rank rose 27 spots (#258 → #231)

2026-07-15

Rank Moved

Rank dropped 13 spots (#245 → #258)

2026-07-14

Rank Moved

Rank dropped 14 spots (#231 → #245)

2026-07-13

Newly Listed

First tracked at rank #231

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Security & Guardrails

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