Multi-dimensional quality scoring for DeepSeek Harness plugins: scores one repo or npm package across install success (consuming dsh-test-drive results), maintenance activity, documentation completeness, security scan, and protocol compliance — every conc
Status: active. This is the local, on-demand prior inspector; the public evidence layer is
dsh-attention-index. No FROZEN banner.
npm i -g dsh1024 once, then dsh1024 plugin --profile web add dsh-score (counts toward the deepseek1024.com install ranking).
Multi-dimensional quality scoring for DeepSeek Harness plugins.
Five dimensions, real gh/npm evidence, one weighted risk card and leaderboard.
English · 简体中文 · Español · Português · हिन्दी
dsh plugin --profile <name> add dsh-score
📖 Ecosystem knowledge base — measured data, not marketing: plugin development guide · plugin-selection data · maintenance criteria.
dsh plugin --profile web add dsh-score # install (npm) — or the git form above
dsh plugin --profile web remove dsh-score # uninstall
这个插件是 DSH 插件家族的一员（95 个，全部 Apache-2.0）。如果你在用，给个 star —— 它不会解锁任何功能，但会让下一个人在搜索里更容易找到它。
English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.
Multi-dimensional quality scoring for DeepSeek Harness plugins.
Five dimensions, real gh/npm evidence, one weighted risk card and leaderboard.
Workflow overview: question → sealed sources → report. The examples below use the real command surface.
| Component | Version |
|---|---|
| DeepSeek Harness | dsh-v0.2.1-rc.2 (GitHub tag). The engines.dsh gate is >=0.2.1-0 <0.3.0; dev/test pins and the typecheck:ci ruler measure 0.2.1-rc.2. The ctx.jobs seam uses the SessionId contract. |
| Node.js | ^22.19.0 || >=24.0.0 |
| Package manager | pnpm@11.7.0 |
| Platform | Windows / macOS / Linux (host-only plugin) |
| External tools | gh CLI on PATH (authenticated for API reads), npm CLI on PATH |
score tool — one target through the five-dimension pipeline; returns the structured risk card, or { kind: 'background', jobId } with background: true./score command — batch scoring of a whitespace/comma-separated target list as a score-batch background job over ctx.jobs, producing a leaderboard snapshot (JSON + Markdown).score_report tool — fetch any stored score card (sc_...), leaderboard (lb_...), or the latest leaderboard.score_badge tool — an embeddable README badge (shields.io flat SVG + endpoint URL) and the five-dimension JSON for one scored target.25, maintenance 20, documentation 20, security 20, compliance 15.source, sanitized detail, observedAt); a dimension without evidence reports no-evidence (score 0, excluded from the weighted total), never a fabricated number.schema: "dsh-score/v1" with first-class fields; this is the machine-readable contract downstream tooling consumes.dsh plugin --profile web add github:PerryLink/dsh-score#<commit-sha>
The first add fails because pnpm blocks the package's prepare build; copy the exact key pnpm printed into the profile's pnpm-workspace.yaml and re-run:
allowBuilds:
'dsh-score': true
dsh plugin --profile web add dsh-score
Prebuilt packages need no build allowance. Restart the profile, then use score / /score from a session.
These are the plugin's real entry points; install once, then call one.
Command
score({ target: "owner/repo" })
Output
# Score sc_65e817eec8cd71ed
- Target: `owner/repo` (repo)
- Grade: **B** — total 88/100
- Verdict: healthy (weighted total 88/100)
| Dimension | Status | Score | Weight | Summary |
|---|---|---|---|---|
| Install success | ⬜ no-evidence | 0 | 25 | no dsh-test-drive result recorded for this target (install success unmeasured) |
| Maintenance | ✅ pass | 100 | 20 | active (2026-08-15T00:00:00.000Z; 0 open issues) |
| Documentation | 🟠 warn | 70 | 20 | 1/4 language READMEs + CHANGELOG + SECURITY |
| Security | ✅ pass | 100 | 20 | license MIT |
| Protocol compliance | ✅ pass | 81 | 15 | dsh.bundle.patch declared |
Observed from README.md:141-149,169-191; tests/tools.spec.ts:64-65; tests/score.spec.ts:50-55; src/report.ts:40-53
Input
{"id":"sc_nope"}
Output
isError=true; error.message=dsh-score: no score recorded with id sc_nope
Observed from plugins/dsh-score/src/tools.ts:351-354 (throw); plugins/dsh-score/tests/tools.spec.ts:95-99 (unknown id); plugins/dsh-score/README.md:179-181 (score_report); exercised through plugins/dsh-score/tests/harness.ts
All keys are optional (defaults shown); invalid values fail loudly at load.
| Key | Default | Description |
|---|---|---|
probeTimeoutMs | 60000 | Deadline for one gh/npm probe command. |
outputTailBytes | 8000 | Cap on the sanitized output tail recorded per probe. |
cacheMaxAgeMs | 86400000 | How long a cached score card is reused before re-scoring (0 disables the cache). |
staleCommitWarnDays | 90 | Commit/publish age at which maintenance drops to warn. |
staleCommitFailDays | 365 | Commit/publish age at which maintenance drops to fail. |
staleIssueWarnDays | 30 | Oldest-open-issue age (response proxy) at which maintenance drops to warn. |
staleIssueFailDays | 180 | Oldest-open-issue age at which maintenance drops to fail. |
maxBatchTargets | 20 | /score batch cap. |
batchConcurrency | 1 | Batch concurrency (serial avoids API-rate contention). |
weights | {install:25, maintenance:20, documentation:20, security:20, compliance:15} | Per-dimension weights (each 0–100; at least one must be > 0). |
scorescore(target: string, refresh?: boolean, background?: boolean)
target — a GitHub repo (github:owner/repo, owner/repo, a git/https URL) or an npm package name.refresh: true bypasses the score cache and re-gathers evidence.background: true starts a score-batch job and returns its id./score <targets...>Starts one background batch job; progress streams through the job output, and the final line names the leaderboard id for score_report.
score_report(id?)Returns a score card (sc_...), a leaderboard (lb_...), or — with no id — the latest leaderboard.
score_badge(target? | id?, refresh?)Generates an embeddable README badge and the five-dimension JSON for one target:
target — score a GitHub repo or npm package (through the cache) and badge it; mutually exclusive with id.id — badge a stored score card (sc_...) without re-scoring.refresh: true — bypass the score cache (only applies to target).Returns the badge (SVG + endpoint + Markdown embed) and the compact five-dimension JSON — see Badge & JSON API.
{
"schema": "dsh-score/v1",
"scoreId": "sc_8f1c2e4a9b3d7f01",
"target": { "kind": "repo", "spec": "github:owner/dsh-click#abc123" },
"scoredAt": "2026-08-16T00:00:00.000Z",
"durationMs": 3210,
"pluginVersion": "0.2.22",
"dimensions": {
"install": { "dimension": "install", "status": "no-evidence", "score": 0, "weight": 25,
"summary": "no dsh-test-drive result recorded for this target (install success unmeasured)",
"evidence": [{ "source": "test-drive", "detail": "no test-drive record found in the test_drive domain", "observedAt": "2026-08-16T00:00:00.000Z" }] },
"maintenance": { "dimension": "maintenance", "status": "pass", "score": 100, "weight": 20,
"summary": "active (2026-08-10T00:00:00Z; 0 open issues)",
"evidence": [{ "source": "gh-api", "detail": "last activity 2026-08-10T00:00:00Z", "observedAt": "2026-08-16T00:00:00.000Z" }] }
},
"total": 88,
"grade": "B",
"verdict": "healthy (weighted total 88/100)"
}
Scoring: the total is a weighted average over dimensions that gathered evidence (no-evidence dimensions are excluded and renormalized); A ≥ 90, B ≥ 75, C ≥ 60, D ≥ 40, else F, and N/A when nothing had evidence.
score_badge generates an embeddable README badge and the five-dimension JSON for one scored target.
Three forms, all derived from the same settled score card:
badge.svg field / renderScoreBadge) for offline or self-hosted READMEs.Embed the total badge in any README:
The same call returns the compact JSON API envelope (schema: "dsh-score/badge/v1"):
{
"schema": "dsh-score/badge/v1",
"target": { "kind": "repo", "spec": "github:owner/dsh-click#abc123" },
"scoredAt": "2026-08-16T00:00:00.000Z",
"total": 84,
"grade": "B",
"dimensions": {
"install": { "label": "install", "status": "no-evidence", "score": 0, "weight": 25, "summary": "no dsh-test-drive result recorded" },
"maintenance": { "label": "maintenance", "status": "pass", "score": 90, "weight": 20, "summary": "active (0 open issues)" },
"documentation": { "label": "docs", "status": "pass", "score": 85, "weight": 20, "summary": "README + CHANGELOG + SECURITY" },
"security": { "label": "security", "status": "warn", "score": 60, "weight": 20, "summary": "permissive license" },
"compliance": { "label": "compliance", "status": "pass", "score": 100, "weight": 15, "summary": "dsh.bundle.patch + dsh-plugin topic" }
}
}
A no-evidence dimension keeps its honest status and score 0 — the badge and JSON never fabricate a number.
ctx.subprocess, ctx.jobs, ctx.storageDomain, ctx.tools, ctx.commands.score storage-domain (tables scores, leaderboards; latest-leaderboard pointer). When the composition has no storageDomain (profiles that predate the base bundle's storage rows, such as the 0.1.1-rc.2-era headless profile), tools still work and score persistence is disabled with a logged reason. The published dsh-base bundle mounts storage-domain from 0.1.2-rc.1 on (verified against the 0.1.2-rc.1 and 0.1.5-alpha.1 tarballs), so persistence is active on the published line.gh reads its own credential store. No environment value is ever logged.gh api and npm view only; it never installs, builds, or runs a target.no-evidence, never a number.gh to be authenticated and network access to GitHub; npm probes require npm and registry access.no-evidence).dsh-test-drive being mounted and having recorded the target; otherwise it is honestly no-evidence.refresh: true (or wait past cacheMaxAgeMs) to force re-scoring.pnpm install
pnpm run typecheck && pnpm run typecheck:ci && pnpm test
pnpm run build && pnpm run verify:self-contained && pnpm run verify:artifacts && pnpm pack
typecheck resolves @deepseek-ai/* through the local harness checkout; typecheck:ci checks against the published 0.1.7-rc.2 types.Context/Session/ToolRuntime/LocalJobRegistry/storage stack with a scripted subprocess provider.gh/npm on PATH, gh authenticated): invoke score from a mounted profile.node scripts/release.mjs <x.y.z> (bumps, stamps CHANGELOG, re-runs the gate, commits + tags; never pushes).dsh, dsh-plugin, deepseek-harness, deepseek, cordis, plugin-scoring, quality-score, leaderboard, supply-chain
PerryLink — design and implementation.
This project is part of the DeepSeek Harness plugin family from PerryLink. The roster stays collapsed below so every README keeps a short first screen; expand it to see every row and its status.
FAQs
Multi-dimensional quality scoring for DeepSeek Harness plugins: scores one repo or npm package across install success (consuming dsh-test-drive results), maintenance activity, documentation completeness, security scan, and protocol compliance — every conc
The npm package dsh-score receives a total of 662 weekly downloads. As such, dsh-score popularity was classified as not popular.
We found that dsh-score demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Threat Research
/Security News
Cursor removed a malicious Claude Code 2.1.313 extension from its marketplace. Socket examines registry records and the initial claims about its distribution.
Security News
An OpenCode user faced harassment after reporting a free AI usage loophole, drawing a bitter backlash in a GitHub thread that has since been deleted.
Threat Research
/Security News
319 browser extensions installed by 13.4 million users hijack searches, capture queries, and collect referral payments from Yahoo and Bing.