DeepSeek Harness

DeepSeek Harness: Everything is a Plugin.

Coding Agents TypeScript Listed MIT

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

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 0%
Last push 2d ago
Advisories None known
Compare DeepSeek Harness
Suggest a correction

In detail: DeepSeek Harness scores 72.6/100 (Grade B), ranked #280 of 1343 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 4.6/10; recent commits are unsigned; no published advisory affects its latest release (@deepseek-ai/dsh); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How DeepSeek Harness 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.

How DeepSeek Harness compares in Coding Agents

  1. #12 Ouroboros (Agent OS) 74.3 +1.7
  2. #13 GPTMe 73.0 +0.4
  3. #14 DeepSeek Harness 72.6 this agent
  4. #15 Tura 71.9 −0.7
  5. #16 Claude Code 70.8 −1.8

Bars show each HVTrust score; the tick marks DeepSeek Harness’s 72.6.

Where the 72.6 comes from

HVTrust dimensions vs the Coding Agents average

72.6 / 100 · 100.0% confidence

DeepSeek Harness Coding Agents average (75 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.8 / 25
3.1 below avg 8.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
0.6 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.1 above avg 14.8
AdoptionLog-scaled stars · package downloads
20.0 / 20
7.8 above avg 12.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
99.9
Activity sub-score · out of 100
#14

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 →

Signals refreshed 2026-10-01 00:09 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-09-30

Activity & Reach

Stars
241.1k
Forks
29.0k
Last Push
2026-09-29
2 days ago
Commits (4 wk)
5412
Downloads (7d)
351,690
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▲3
was #283

Analysis

Activity Inputs

99.9 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
20 / 20

Supply Chain Trust

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

Common questions about DeepSeek Harness

DeepSeek Harness 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 DeepSeek Harness publish package provenance?
No published build provenance is currently detected for DeepSeek Harness. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DeepSeek Harness have an OpenSSF Scorecard?
DeepSeek Harness has an OpenSSF Scorecard score of 4.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 DeepSeek Harness actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does DeepSeek Harness use?
DeepSeek Harness ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DeepSeek Harness's commits signed?
0% of the last 100 commits to DeepSeek Harness 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
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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
How this surface has changed

Detected changes to DeepSeek Harness'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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

Maintain DeepSeek Harness?

For maintainers

HVTrust scores DeepSeek Harness 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 11Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: DeepSeek
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 301 spots (#571 → #270)
2026-09-23
HVTrust Changed
HVTrust up 37.1pts (35.6 → 72.7)
2026-09-22
Newly Listed
First tracked at rank #571
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 11 spots (#261 → #272)
2026-09-07
Rank Moved
Rank dropped 15 spots (#234 → #249)
2026-09-05
Rank Moved
Rank dropped 55 spots (#181 → #236)
2026-09-03
Rank Moved
Rank dropped 11 spots (#165 → #176)
2026-08-31
Rank Moved
Rank dropped 23 spots (#139 → #162)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-29
Grade Changed
Trust grade D → B
2026-08-29
Rank Moved
Rank rose 576 spots (#723 → #147)
2026-08-29
HVTrust Changed
HVTrust up 29.6pts (43.0 → 72.6)
2026-08-28
Rank Moved
Rank dropped 27 spots (#696 → #723)
2026-08-27
Rank Moved
Rank dropped 16 spots (#680 → #696)
2026-08-26
Rank Moved
Rank dropped 94 spots (#586 → #680)
2026-08-24
Rank Moved
Rank dropped 10 spots (#576 → #586)
2026-08-16
Newly Listed
First tracked at rank #589

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/deepseek-harness.svg)](https://hvtracker.net/agents/deepseek-harness)
HTML:
<a href="https://hvtracker.net/agents/deepseek-harness"><img src="https://hvtracker.net/badge/deepseek-harness.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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