Install verification: sandbox install failed (L4) · tested on dsh 0.1.7-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Manages dsh web profile configuration files with Git and provides one-click installation scripts.
- Uses Git to version control profile config files
- Provides install.sh for clone or worktree install
- Supports remote curl one-click installation
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:Yiklek/dsh-web-profileInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.1.7-rc.2
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.
current (registry 2026-11-19) · 7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-16 · 7 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-06 → 11-16 · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 | dsh 0.1.5-rc.2 |
|---|---|---|---|---|---|
| dsh-v0.1.7-rc.2 | · | · | · | · | · |
| a6a9e9 | ✗ | ○ | ✗ | ✗ | ✗ |
| 6dbf58 | · | · | · | · | · |
dsh-v0.1.7-rc.2github2026-11-14
https://github.com/Yiklek/dsh-web-profile
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
a6a9e9github9 failed2026-09-29
https://github.com/Yiklek/dsh-web-profile
✗dsh 0.1.7-rc.22026-09-25L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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-rc.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@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-20L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.12026-09-16L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
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.5-rc.22026-09-11L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.3-alpha.22026-09-08L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.3-alpha.12026-09-07L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
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.2-rc.12026-09-05L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile#a6a9e9
ID: dsh-web-profile@a6a9e9@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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.2-alpha.12026-09-06L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile (version unstated)
ID: dsh-web-profile@a6a9e9@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
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.1-rc.22026-08-28L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/Yiklek/dsh-web-profile#a6a9e9
ID: dsh-web-profile@a6a9e9@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.
6dbf58github2026-08-24
https://github.com/Yiklek/dsh-web-profile
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-web-profile/?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 high; dynamic medium (authoritative when present) → overall medium.
v0.0.0dsh manifestdsh-v0.1.7-rc.2git2026-11-19dsh-v0.1.7-rc.2same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalpipeShell · shell
install.sh:53When run via `curl ... | bash`, the script uses the default remote - criticalpipeShell · shell
install.sh:61curl -fsSL https://raw.githubusercontent.com/Yiklek/dsh-web-profile/main/install.sh | bash -s -- [profile-name] [options] - criticalpipeShell · shell
install.sh:72curl -fsSL https://raw.githubusercontent.com/Yiklek/dsh-web-profile/main/install.sh | bash -s -- web - warningchildProcess · code-exec
packages/openviking-service/index.mjs:66const result = spawnSync(command, ["--version"], { - warningchildProcess · code-exec
packages/openviking-service/index.mjs:157const child = spawn( - warningnetIp · network
packages/openviking-service/index.mjs:6const DEFAULT_ENDPOINT = "http://127.0.0.1:1933"; - warningnetIp · network
scripts/install-services.mjs:814url: `http://127.0.0.1:${OPENVIKING_DEFAULT_PORT}`,
show 3 audit findings
- mediumUnpinned `uvx --from openviking[local-embed]` executes the latest PyPI release at every DSH start
packages/openviking-service/index.mjs:162Once OpenViking is enabled (--openviking / DSH_ENABLE_OPENVIKING=1), this runtime plugin resolves `openviking[local-embed]` from PyPI on each start and executes the resulting code (including a source-built llama-cpp-python) with the user's privileges, with no version or hash pin. The installer pins the same runtime at 0.4.22 (scripts/install-services.mjs:167), so the intended pin is not enforced on the path that actually runs, leaving a supply-chain / version-drift exposure at session start.
- lowDeepSeek API key is copied from the credential store into a plaintext profile config inside a git working tree
scripts/install-services.mjs:805When OpenViking is enabled, the DEEPSEEK_API_KEY from ~/.dsh/.credentials.yaml or the environment is persisted as plaintext into `<profile>/.services/openviking/ov.conf`. In clone/worktree installs that profile root is a git working tree of a repository, so a stray `git add -A` or a copy of the profile directory propagates the secret; the file itself is written 0600, and the whole path is opt-in, which limits the impact.
- lowUnvalidated profile name is concatenated into filesystem paths and used by `mv` in backup_profile
install.sh:174PROFILE_NAME comes straight from the positional argument with no character check. A name containing `..` or `/` (e.g. `../../../Documents`) builds a PROFILE_DIR outside ~/.dsh/profiles, and with --force the existing-directory branch moves that unrelated directory to `<name>.bak.<timestamp>` before cloning. Exploitation requires the user to pass the crafted name themselves, so this is a local self-inflicted footgun rather than a remote vector.
No critical issue: install/config scripts stay shell-free with fixed argv; residual risk is an unpinned uvx runtime fetch and the DeepSeek key persisted in plaintext in the profile.
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-11-17 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 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-web-profile?
dsh-web-profile 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-web-profile?
Run dsh plugin --profile web add github:Yiklek/dsh-web-profile#dsh-v0.1.7-rc.2 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-19 (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.
