Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Migrates DSH plugins between profiles (web→desktop): diffs plugin sets, preflights, generates an after-exit install script, then verifies after restart.
- Diffs plugin sets between a source and target profile
- Preflight checks plus an after-exit install script it generates
- Post-restart verification that the last migration actually landed
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:wbb316/dsh-profile-sync#v0.2.1Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.1
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.
5 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-01 → 11-05 · 5 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-15 → 11-05 · 4 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 3 @deepseek-ai/dsh-* packages. raw ranges
>=0.2.0-rc.1 ×3
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
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.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v0.2.1 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.1.0 | · | · | · | · | · |
v0.2.1github✓ 7 runtime-verified2026-11-14
https://github.com/wbb316/dsh-profile-sync
✓dsh 0.2.2-rc.12026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.2.1
ID: dsh-profile-sync@v0.2.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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.1.0github✓ 2 runtime-verified2026-10-09
https://github.com/wbb316/dsh-profile-sync
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.1.0
ID: dsh-profile-sync@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/wbb316/dsh-profile-sync#v0.1.0
ID: dsh-profile-sync@v0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-08
View checks & evidence
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-profile-sync@v0.2.1@dsh0.2.2-rc.3 (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.
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-profile-sync/?ref=badge)``[](https://www.dsh.so/artifact/dsh-profile-sync/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-profile-sync/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-profile-sync/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-profile-sync/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-profile-sync/?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.2.1dsh manifestv0.2.1git2026-11-15v0.2.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalspawnShell · shell
bin/bootstrap.mjs:166const res = spawnSync(cmdline, { shell: true, stdio: 'inherit', cwd: profileDir, windowsHide: false }) - warningchildProcess · code-exec
bin/apply.mjs:72const res = spawnSync(cmdline, { - warningchildProcess · code-exec
bin/bootstrap.mjs:166const res = spawnSync(cmdline, { shell: true, stdio: 'inherit', cwd: profileDir, windowsHide: false }) - warningnetIp · network
bin/bootstrap.mjs:104const base = `http://127.0.0.1:${port}` - warningchildProcess · code-exec
bin/verify-client.mjs:187const child = spawn(process.execPath, [dshBin, ...argsList], { - warningchildProcess · code-exec
bin/verify-client.mjs:389server = spawn(process.execPath, [dshBin, '--profile', profile, '--patch', overlayFile, '--no-open'], { - warningshellExec · shell
bin/verify-client.mjs:128const root = execFileSync('npm', ['root', '-g'], { encoding: 'utf8', windowsHide: true }).trim() - warningshellExec · shell
bin/verify-client.mjs:135const where = execFileSync(process.platform === 'win32' ? 'where' : 'which', ['dsh'], { - warningshellExec · shell
bin/verify-client.mjs:295out = execFileSync(browser, [...recipe.flags, ...common], { - warningnetIp · network
bin/verify-client.mjs:362if (await waitForHttp(`http://127.0.0.1:${port}/`, 1500)) { - warningnetIp · network
bin/verify-client.mjs:403const base = `http://127.0.0.1:${port}` - warningnetIp · network
bin/verify-client.mjs:427url = `http://127.0.0.1:${tokenMatch[1]}/?token=${tokenMatch[2]}`
show 3 audit findings
- mediumPOST /profile-sync/api/apply has no origin check and applies the full default migration on an empty or malformed body
lib/index.jsreadBody turns an empty or non-JSON body into {}; safePlan({}) then defaults to source='web' and target=currentProfileName(), canApplyInApp() passes for the current profile, and applyManaged() installs every missing plugin into the running profile through the official manager. The handler never checks Origin/Referer, so any local process or any page able to POST to the host web server can trigger a full migration with no confirmation, without using the panel. Reachability depends on the host webServer's own auth (not verifiable from the harvested files), which is why this is medium rather than
- lowShell command string built by concatenation in bin/apply.mjs and bin/bootstrap.mjs (spawnSync shell:true)
bin/apply.mjs:71Command lines are assembled as strings and executed through cmd.exe/sh. Today the interpolated values are constrained: profile names are checked by isProfileName() (applyPlan throws before the runner is used) and bootstrap.mjs validates the name with the same helper, while the link: spec is derived from the script's own directory. --dsh is an explicit user argument. So no attacker-controlled injection is demonstrated, but any future weakening of isProfileName() or of the plan-validation path turns this into command execution.
- lowverify-client.mjs recursively deletes any profile directory the user names, guarded only by a 6-name deny-list
bin/verify-client.mjsThe script is documented as using a throwaway profile, but --profile accepts any name outside FORBIDDEN_PROFILES (desktop/web/headless/default/main/tui). Passing a real profile such as a custom 'work' or 'desktop-dev' profile deletes it (and its node_modules) before the verification run. This is user-initiated data loss, not a remote attack.
Well-guarded profile-migration plugin (snapshots, rollback, plan validation, no outbound network), but a state-changing HTTP apply route accepts an empty body with no origin check.
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-10-06 · activity: Stable
• Repo created: 2026-09-30
• Stars: ★ 5 · 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 @wbb316/dsh-profile-sync?
@wbb316/dsh-profile-sync 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 @wbb316/dsh-profile-sync?
Run dsh plugin --profile web add github:wbb316/dsh-profile-sync#v0.2.1 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-15 (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.
