Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Local GPU-accelerated background removal tool for images using rembg.
- Local rembg GPU service
- Removes image backgrounds
- Image segmentation support
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.
Installation
dsh plugin --profile web add github:H-table/dsh-bg-toolInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.3
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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
6 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-05 · 6 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-01 → 11-05 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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 2 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×2
✗ Running dsh 0.2.2-rc.3 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-bg-tool@1.0.0 0.2.2-rc.3 (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.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 403b76 | · | · | · | · | · |
| 3b84c5 | ✗ | ✗ | ✗ | ✗ | ✗ |
403b76github2026-08-24
https://github.com/H-table/dsh-bg-tool
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
3b84c5github◐ 1 testing16 failed2026-11-14
https://github.com/H-table/dsh-bg-tool
✗dsh 0.2.1-rc.32026-10-27L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.22026-10-21L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
This level was not executed in this scan.
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
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-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-alpha.22026-09-23L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.6-alpha.12026-09-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.22026-09-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.3-alpha.12026-09-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-rc.12026-09-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool#3b84c5
ID: dsh-bg-tool@3b84c5@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-alpha.12026-09-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool#3b84c5
ID: dsh-bg-tool@3b84c5@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/H-table/dsh-bg-tool (version unstated)
ID: dsh-bg-tool@3b84c5@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-bg-tool/?ref=badge)`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.
v1.0.0dsh manifest1.0.0git2026-11-171.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalnewFunction · code-exec
validate-client.mjs:24const fn = new Function('window', 'require', code); - warningchildProcess · code-exec
lib/index.js:115const child = spawn(python, [script], { - warningnetIp · network
lib/index.js:52const API = 'http://127.0.0.1:7000/api/remove'; - warningnetIp · network
lib/index.js:53const HEALTH = 'http://127.0.0.1:7000/openapi.json';
show 3 audit findings
- mediumPlugin-owned settings route mutates settings with no in-handler auth, origin or CSRF check
lib/index.js:203handleSettingsRequest() only checks the HTTP method and body.action; it never verifies a session, Origin/Referer or a CSRF token before applying caller-supplied mutate ops for the 'bg-tool' namespace. Any client that can reach the DSH web origin (another local process, or a browser page issuing a simple text/plain POST to the loopback port) can rewrite generalModel/portraitModel/fastModel, outputDir and autoStartServer. Because outputDir is later used as the write target of remove_background (fsp.mkdir/fsp.writeFile), the write also becomes an arbitrary-directory PNG-drop primitive for the DSH
- lowExecuted pythonw.exe/bg_server.py path derives from DSH_BG_TOOL_ROOT and a hardcoded legacy directory
lib/index.js:102startServerProcess() runs the binary and script found under BG_ROOT, and BG_ROOT is taken from process.env.DSH_BG_TOOL_ROOT when set (resolveBgRoot, line 42) or from the hardcoded fallback 'E:/ProjectCode/DeepSeekHarnessWorkbook/.bg-tools' when that directory exists (line 47). Anyone who can set the DSH process environment, or who can write a venv/Scripts/pythonw.exe + bg_server.py pair into that legacy workspace directory, gains code execution as the DSH user at plugin load. The precondition (control over the host env or that specific directory) means this is not remotely reachable on its own
- lowDev-only validation script executes the client bundle through new Function
validate-client.mjs:24The harness reads a file from a hardcoded absolute path and evaluates it with new Function to exercise the __ModuleLoader__ protocol. This is a dynamic-evaluation construct that static scanners flag, but it is a development tool: it is not referenced by package.json 'files' (only lib and cordis.patch.yml are published), is not imported by lib/index.js or lib/client.js, and takes no external input, so there is no reachable production impact.
Legit local rembg tool; its own settings route has no in-handler auth/CSRF check, and the spawned python path derives from an env var, but no RCE or exfiltration was found.
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-08-19 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/H-table/dsh-bg-tool
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 dsh-bg-tool?
dsh-bg-tool 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 dsh-bg-tool?
Run dsh plugin --profile web add github:H-table/dsh-bg-tool 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-17 (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.
