Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Linux backend providing bubblewrap sandbox recipes and chattr-based file attributes for verifiable claims.
- Bubblewrap-based process isolation sandboxing
- Uses chattr for file attribute integrity
- Each claim carries an experiment number
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:Wang-Lin-Chang/dsh-cross-platform#v0.1.0Install method: GitHub · runtime test inconclusive (L5 unknown)
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.
9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-05 · 9 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
09-28 → 11-05 · 8 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○ Ecosystem plugin
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.0 | ○ | ○ | ○ | ○ | ○ |
v0.1.0github○ 16 ecosystem plugin2026-11-16
https://github.com/Wang-Lin-Chang/dsh-cross-platform
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
not present in web-profile loader inventory
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
not present in web-profile loader inventory
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
not present in web-profile loader inventory
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Wang-Lin-Chang/dsh-cross-platform#v0.1.0
ID: dsh-cross-platform@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-cross-platform/?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.
v0.1.0v0.1.0git2026-11-17v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningchildProcess · code-exec
src/detach-runner-linux.cjs:16const sh = (c) => { try { return spawnSync('sh', ['-c', c], { timeout: 10000 }).stdout.toString().trim() } catch { return '' } } - warningchildProcess · code-exec
src/detach-runner-linux.cjs:81const child = spawn(useBwrap ? 'bwrap' : 'bash', taskArgs, { stdio: ['ignore', 'pipe', 'pipe'], cwd: jobDir }) - warningfsWrite · files
src/detach-runner-linux.cjs:33fs.writeFileSync(lockFile, `${process.pid}:${startSec()}`, { flag: 'wx' }) - warningfsWrite · files
src/detach-runner-linux.cjs:39try { fs.writeFileSync(exitFile, '', { flag: 'wx' }) } catch {} - warningshellExec · shell
src/linux-backend.mjs:17try { return execFileSync('sh', ['-c', cmd], { timeout: 10000 }).toString().trim() } catch (e) { throw new Error(`sh fail: ${String(e.stderr - warningfsWrite · files
src/linux-utils.mjs:29try { fs.writeFileSync(file, `EXIT:${code}`) } catch {}
show 4 audit findings
- mediumMissing bwrap silently degrades to fully unsandboxed command execution
src/detach-runner-linux.cjs:81When mode is 'bwrap' but the bwrap binary is absent (sh('which bwrap') returns '' on any error), useBwrap becomes false and the task command is executed by plain 'bash -c' with only chattr +i on exit.txt/lock as protection. The task then runs with the runner's full privileges, unrestricted filesystem write access and network, i.e. the advertised namespace isolation is silently absent with no error, no EXIT marker and no disclosure to the caller.
- mediumTask namespace bind-mounts the whole host filesystem read-only and keeps full network
src/detach-runner-linux.cjs:79Every sandboxed task gets a read-only view of the entire host root, including /home/*/.ssh, /etc, other jobs' directories under jobDir's parent and any credential files, and --share-net deliberately keeps full outbound network. A malicious or compromised task can therefore read host secrets and exfiltrate them over the network in one step, which contradicts the file's claim of 'whole FS view read-only' as a containment boundary.
- mediumLinuxSandboxBackend interpolates jobDir/file paths into 'sh -c' without any escaping
src/linux-backend.mjs:31A single quote in jobDir (or in the file name built from it) terminates the single-quoted string and the remainder is executed by /bin/sh with the plugin's privileges, e.g. jobDir = "/tmp/x'; touch /tmp/pwned; '". The runner file next to it implements proper escaping via q(), but this backend does not, so the only protection is the assumption that jobDir is always host-generated and quote-free — an assumption never validated anywhere in the plugin.
- lowChild 'error' handler leaves an immutable lock file and leaked fds, blocking later jobs
src/detach-runner-linux.cjs:98If spawn fails (e.g. bwrap present per 'which' but not executable), the handler neither clears the immutable bit on lock nor unlinks it, and leaves outFd unclosed. Because lock creation uses the exclusive 'wx' flag, a stale lock makes every subsequent job in that directory fail to acquire the lock, a persistent local denial of service that requires manual cleanup.
Linux sandbox backend: silent unsandboxed fallback, whole-host ro-bind plus network for tasks, and unescaped jobDir interpolation into sh -c.
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-26 · activity: Stable
• Repo created: 2026-08-16
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
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-cross-platform?
dsh-cross-platform is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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-cross-platform?
Run dsh plugin --profile web add github:Wang-Lin-Chang/dsh-cross-platform#v0.1.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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.
