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
TPM/DPAPI-sealed credential provider for DeepSeek Harness that replaces plaintext credential files with hardware-backed sealed storage.
- Seals credentials with TPM or DPAPI hardware protection
- Replaces plaintext credential files in DeepSeek Harness
- Acts as a drop-in credential provider plugin
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.
6 samples (roughly every 7 days), 1 of them reconstructed (hollow dots); sampled points, not a daily series
10-01 → 11-07 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-10 → 11-07 · 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
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:rickwindman/dsh-destinywind-tpmInstall method: GitHub · 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 4 @deepseek-ai/dsh-* packages. raw ranges
^0.1.5-rc.1 ×4
✗ 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-destinywind-tpm@1.0.0 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 |
|---|---|---|---|---|---|
| 3d2910 | ✗ | ✗ | ✗ | ✗ | ✗ |
3d2910github9 failed2026-11-04
https://github.com/rickwindman/dsh-destinywind-tpm
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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/rickwindman/dsh-destinywind-tpm (version unstated)
ID: dsh-destinywind-tpm@3d2910@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-destinywind-tpm@3d2910@dsh0.2.2-rc.1 (l3-fullscan)
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-destinywind-tpm/?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 high (authoritative when present) → overall high.
v1.0.0dsh manifest1.0.0git2026-11-111.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
dpapi.js:63const child = spawn(shell, ['-NoProfile', '-NonInteractive', '-EncodedCommand', encodeCommand(script)], { - warningbase64Decode · obfuscation
dpapi.js:36'$bytes = [Convert]::FromBase64String($raw)', - warningchildProcess · code-exec
linux.js:37const child = spawn(command, args, { stdio: ['pipe', 'pipe', 'pipe'] }) - warningchildProcess · code-exec
tpm.js:94const child = spawn(shell, ['-NoProfile', '-NonInteractive', '-EncodedCommand', encodeCommand(script)], { - warningbase64Decode · obfuscation
tpm.js:51'$bytes = [Convert]::FromBase64String($raw)',
show 3 audit findings
- highLinux keyring backend returns the raw data key, so the store file contains the AES master key in cleartext
linux.js:173When no usable tpm2-tools backend exists, the protector's seal() is a no-op: index.js dataKeyLocked() takes the returned buffer and stores it base64-encoded in the `key` field of .credentials.dpapi.json (unsealBytes ignores the blob and only re-reads the keyring). Anyone who obtains that file — a backup, a sync folder, a copy on another machine, or another local account able to read it — can base64-decode the 32-byte key and decrypt every ref and record with node:crypto, using the entry name as AAD. The plugin's core claim that the store is unreadable without the OS user's credential does not
- mediumTPM probe recreates a machine-global key with OverwriteExistingKey and can permanently orphan existing stores
tpm.js:68tpmAvailable() calls createKey() whenever selectProtector() runs, which happens on every mount where the store still has no sealed key (probe() with no sealedKey, or the first write). The wrapping key name is fixed per machine, so initializing a second store (a second DSH home, the configurable `path`, or a store file that was moved/restored) silently replaces the key and every ciphertext previously written under it becomes permanently undecryptable — irreversible loss of saved credentials.
- lowLinux artefact directory falls back to /tmp and temp files use predictable names with default mode and no symlink protection
linux.js:141mkdir(dir, { recursive: true, mode: 0o700 }) does not tighten a directory that already exists and does not fail when an attacker pre-created it; when HOME is unset the whole artefact tree lives under world-writable /tmp. Temp files are opened by a predictable name with the default mode (0666 & umask) and without O_NOFOLLOW/O_EXCL, so a local attacker who can write in that directory (pre-created dir, or a loosely-permissioned existing .dsh tree) can plant a symlink or a world-readable file to obtain the key blob written there or to clobber a victim file with key material.
Linux keyring fallback stores the raw AES data key in the on-disk JSON, so all sealed credentials are recoverable from the file alone; TPM key reuse can also destroy existing stores.
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-26 · activity: Stable
• Repo created: 2026-09-26
• 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 @rickwindman/dsh-destinywind-tpm?
@rickwindman/dsh-destinywind-tpm 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 @rickwindman/dsh-destinywind-tpm?
Run dsh plugin --profile web add github:rickwindman/dsh-destinywind-tpm 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.