DeepCode

"DeepCode: Open Agentic Coding (Paper2Code & Text2Web & Text2Backend)"

Coding Agents Python Grade C Listed MIT
59.3/100
Rank #322 of 1204
Compare DeepCode

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-09 · 0d ago
Recent change
Rank +5

Is DeepCode safe? DeepCode scores 59.3/100 (Grade C), ranked #322 of 1204 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 4.9/10; 26% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-08
Rank Moved
Rank dropped 83 spots (#245 → #328)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Brave Search
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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.
90.4
Activity sub-score · out of 100
#29

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 →

Signals refreshed 2026-08-09 19:31 UTC · Repo last pushed today

Activity & Reach

Stars
16.3k
Forks
2.1k
Last Push
2026-08-09
today
Commits (4 wk)
93
Downloads (7d)
HN mentions (30d)
Open Issues
15
Rank Change
▲6
was #328

Analysis

HVTrust Dimensions vs Coding Agents

59.3 / 100 · 100.0% confidence

DeepCode Coding Agents average (65 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.4 / 25
0.5 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.7 / 17
1.5 above avg 11.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.8 above avg 15.1
AdoptionLog-scaled stars · package downloads
10.1 / 20
2.2 below avg 12.3

Activity Inputs

90.4 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
24.6 / 25
CommunityFork signal
15.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
26%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 5
CII-Best-Practices 0
Code-Review 4
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 2
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is DeepCode safe?

DeepCode 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 DeepCode publish package provenance?
No published build provenance is currently detected for DeepCode. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepCode have an OpenSSF Scorecard?
DeepCode has an OpenSSF Scorecard score of 4.9/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 DeepCode actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does DeepCode use?
DeepCode ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepCode's commits signed?
26% of the last 100 commits to DeepCode 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
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 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
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
How this surface has changed

Detected changes to DeepCode'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-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Brave Search
2026-08-07
Mcp Status Changed
Detected MCP server support changed: implemented → declared

Maintain DeepCode?

For maintainers

HVTrust scores DeepCode 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

Signal history
Rank 6Score 2Listed 1MCP 1Surface 1Surface 1
2026-08-08
Rank Moved
Rank dropped 83 spots (#245 → #328)
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: declared → extension-based
2026-08-07
Provider Removed
Runtime surface shrank — no longer detected: Brave Search
2026-08-07
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-08-06
Rank Moved
Rank rose 13 spots (#258 → #245)
2026-08-02
Rank Moved
Rank rose 13 spots (#263 → #250)
2026-07-15
Rank Moved
Rank dropped 10 spots (#240 → #250)
2026-07-14
Rank Moved
Rank dropped 14 spots (#226 → #240)
2026-07-13
Rank Moved
Rank dropped 29 spots (#197 → #226)
2026-07-08
Activity Score Changed
Activity score up 7pts (78 → 84)
2026-07-05
Activity Score Changed
Activity score up 19pts (59 → 78)
2026-06-24
Newly Listed
First tracked at rank #234

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 59.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/deepcode.svg)](https://hvtracker.net/agents/deepcode)
HTML:
<a href="https://hvtracker.net/agents/deepcode"><img src="https://hvtracker.net/badge/deepcode.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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.2 · Raw JSON