Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
A bug-fix pipeline for DeepSeek Harness with gated stages, evidence capture and a reviewed pull request, plus shared code2graph and PR cores.
- Gated bug-fix pipeline with evidence at every stage
- Produces a reviewed pull request from the fix run
- Shared c2g/PR cores with Kilo and Hermes frontends
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling (a rotating daily shard); the npm pair from every snapshot.
9 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-28 → 11-08 · 9 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-03 → 11-08 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-26 → 11-09 · 41 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-26 → 11-11 · 42 points
Installation
dsh plugin --profile web add dsh-drillInstall method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
Based on 1 requirement(s) across 3 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0 || >=0.1.6-0 <0.2.0 || >=0.1.7-0 <0.2.0 ×3
✗ Running dsh 0.2.2-rc.1 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-drill-kit@0.8.3 0.2.2-rc.1 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.8.3 | · | · | ✓ | ✓ | ✓ |
| v0.8.3 | · | · | · | · | · |
0.8.3npm✓ 7 runtime-verified2026-11-04
dsh-drill
✓dsh 0.2.1-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-drill@0.8.3
ID: dsh-drill-kit@0.8.3@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-drill-kit@0.8.3@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.8.3github2026-09-25
https://github.com/EnRaiha/dsh-drill-kit
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-drill-kit/?ref=badge)``[](https://www.dsh.so/artifact/dsh-drill-kit/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drill-kit/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drill-kit/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-drill-kit/?ref=badge-install)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic medium (authoritative when present) → overall medium.
v0.8.3dsh manifest0.8.3npm2026-11-110.8.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningshellExec · shell
lib/c2g.js:196const out = execFileSync(sqliteBin, ['-readonly', '-json', db, sql], { encoding: 'utf8', timeout: timeoutMs, maxBuffer: 32 * 1024 * 1024 }) - warningshellExec · shell
lib/embed.js:72const out = execFileSync(sqliteBin, ['-readonly', '-json', path, sql], { encoding: 'utf8', timeout: timeoutMs, maxBuffer: 32 * 1024 * 1024 } - warningshellExec · shell
lib/git.js:20return execFileSync('git', ['-C', repo, ...args], { encoding: 'utf8', timeout: 30_000 }).trim() - warningshellExec · shell
lib/pr.js:121const stdout = execFileSync(python, [core, 'lint-desc', '--stdin'], { - warningchildProcess · code-exec
lib/runner.js:33const child = spawn(shell, ['-lc', command], { cwd, detached: true, stdio: ['ignore', 'pipe', 'pipe'] }) - warningshellExec · shell
lib/search.js:146const stdout = execFileSync(bin, args, { encoding: 'utf8', timeout: options.timeoutMs ?? 600_000, maxBuffer: 8 * 1024 * 1024 }) - warningshellExec · shell
lib/search.js:263raw = execFileSync(resolved.bin, args, { encoding: 'utf8', timeout: options.timeoutMs ?? 30_000, maxBuffer: 32 * 1024 * 1024 })
show 3 audit findings
- mediumrunCapture runs any caller-supplied command line through bash -lc and writes to an unchecked logPath
lib/runner.js:33The module exists to run a command line under /bin/bash with the harness user's full environment; `cwd` is passed through unvalidated and `logPath` is created with mkdirSync + createWriteStream({flags:'w'}), so a caller-supplied path outside the task directory is created or truncated. The library layer imposes no allowlist on `command`, no confinement of `cwd` to the worktree and no containment of `logPath` under the task logs. Running the project's test command is the plugin's stated purpose, so this is a designed capability rather than a hidden backdoor, but the tool-level validation lives i
- lowPR_CRAFT_CORE environment variable selects a file executed with python3
lib/pr.js:26lintPrBody runs `execFileSync(python, [core, 'lint-desc', '--stdin'])` on whatever path DEFAULT_PR_CORE resolves to. The env override, or a replaceable `~/scripts/pr_craft.py` fallback when the bundled core is absent, gives code execution in the harness process to anyone able to influence the plugin's environment or that home-directory file. Requires environment/file control, hence low.
- lowpruneDir recursively deletes children of a caller-supplied base directory without containment check
lib/cache.js:116pruneIndexes forwards options.baseDir into pruneDir, which deletes every child older than the TTL with a recursive force remove. Nothing asserts that the base directory sits under the drill cache root, so a misconfigured cacheDir/baseDir could silently delete unrelated user directories (e.g. anything older than a week under a wrongly pointed path).
Drill plugin legitimately runs shell commands and external scripts; both paths are unconfined and the tool-wiring file index.js was not harvested, so reachability could not be fully verified.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-09-25 · activity: Stable
• Repo created: 2026-09-25
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/EnRaiha/dsh-drill-kit
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is @EnRaiha/dsh-drill-kit?
@EnRaiha/dsh-drill-kit is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install @EnRaiha/dsh-drill-kit?
Run dsh plugin --profile web add dsh-drill in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-11 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.