Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Adds per-workspace password locks to the DSH web UI with right-click locking, a lock screen, and an admin master password.
- Right-click a workspace to lock it behind a password
- Dedicated lock screen blocks access to locked workspaces
- Admin master password for overriding workspace locks
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.
4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-30 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 2 points (< 3): no chart yet
10-01 → 10-09 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:HyperForce/dsh-workspace-lockInstall method: GitHub · runtime verified (L5)
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| d8e63b | ✓ | ✓ | ✓ | ✓ | ✓ |
d8e63bgithub✓ 11 runtime-verified2026-11-05
https://github.com/HyperForce/dsh-workspace-lock
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
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/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
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/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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/HyperForce/dsh-workspace-lock (version unstated)
ID: dsh-workspace-lock@d8e63b@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
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-workspace-lock/?ref=badge)``[](https://www.dsh.so/artifact/dsh-workspace-lock/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-workspace-lock/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-workspace-lock/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-workspace-lock/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-workspace-lock/?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.4.2dsh manifest0.4.2git2026-11-050.4.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticaleval · code-exec
smoke/smoke_client.js:133eval(fs.readFileSync(path.join(__dirname, '..', 'dsh-workspace-lock', 'lib', 'client.js'), 'utf8'));
show 4 audit findings
- mediumLock list endpoint returns salts and password hashes to any admitted client
lib/index.js:201The client only needs the lock keys (it tests them with Object.prototype.hasOwnProperty.call(locks, id)), yet the response contains every entry's {s,h,t}: the salt and salted SHA-256 of each workspace password. SHA-256 is a fast KDF, so weak/reused passwords are crackable offline by anyone who can call /list.
- mediumFirst-time admin-set requires no authentication and mints a master password
lib/index.js:304Any requester that passes the header-only fence (any non-browser client, see the sameOrigin finding) can set the admin password before the operator does. That password then verifies for unlock/remove of ANY workspace and for /unlock-all, and because re-setting/clearing demands the current value, the legitimate operator loses control of the setting until the storage file is edited by hand.
- mediumPOST /set overwrites an existing workspace lock without verifying the current password
lib/index.js:214Any client able to call the route can re-key a workspace that is already locked (the previous password stops working; without an admin master the lock can then only be removed by editing the file) or lock an arbitrary workspace id, hiding that workspace's sessions in the UI for every user — a persistent, reversible-only-by-file-edit UI-level DoS / lock hijack.
- lowsameOrigin fence admits any request with no Origin and no Sec-Fetch-Site header
lib/index.js:100The check distinguishes browsers only. A curl call, any local process, or a LAN peer (if the web server is bound beyond loopback) is treated as same-origin, so sameOrigin() is not an authentication control and every /api/workspace-locks/* route above is reachable by whoever can open the port.
Host routes leak salted password hashes, allow unauthenticated first-time admin-set and unauthenticated lock overwrite; the static critical was an eval in a non-shipped smoke harness.
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-02 · activity: Stable
• Repo created: 2026-09-20
• 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 @HyperForce/dsh-workspace-lock?
@HyperForce/dsh-workspace-lock 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 @HyperForce/dsh-workspace-lock?
Run dsh plugin --profile web add github:HyperForce/dsh-workspace-lock 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-05 (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.