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
A skippable full-screen startup splash animation plugin for DSH, implemented purely as a plugin and toggleable in the plugin library.
- Full-screen splash animation on DSH startup
- Animation can be skipped by the user
- Pure plugin, toggled on/off in the plugin library
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:52baihehhh-ai/dsh-splash-screen#v1.0.0Install 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.
6 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-06 → 11-08 · 6 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-11 → 11-08 · 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
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.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 |
|---|---|---|---|---|---|
| v1.0.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v1.0.0github✓ 9 runtime-verified2026-11-14
https://github.com/52baihehhh-ai/dsh-splash-screen
✓dsh 0.2.2-rc.12026-11-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (200 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/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.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-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/52baihehhh-ai/dsh-splash-screen#v1.0.0
ID: dsh-splash-screen@v1.0.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-splash-screen@v1.0.0@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-splash-screen/?ref=badge)``[](https://www.dsh.so/artifact/dsh-splash-screen/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-splash-screen/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-splash-screen/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-splash-screen/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-splash-screen/?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 low (authoritative when present) → overall low.
v1.0.0dsh manifestv1.0.0git2026-11-14v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalnewFunction · code-exec
client.js:32new Function(SPLASH_SOURCE)()
show 3 audit findings
- lownew Function() evaluates an embedded build-time constant (static-scan 'critical' refuted)
client.js:32Dynamic evaluation is present, but the argument (SPLASH_SOURCE) is a hard-coded, build-generated literal; no user, network or file input reaches it. Real consequences are limited to review difficulty (the whole splash module is nested/escaped as a string, making the client half opaque to static readers) and a hard requirement for a CSP that allows 'unsafe-eval', where the plugin silently degrades to no splash instead of executing anything hostile.
- lowHost half injects a head script that hides the host boot card and paints a full-screen overlay
index.js:121The injected script runs before the app, hides elements of the host's own boot UI (selector scoped to [data-dsh-boot], failure state intentionally left visible) and installs capture-phase keydown/pointerdown/wheel/touchstart listeners that preventDefault/stopPropagation for the ~4.2 s lifetime of the splash. This is the plugin's declared purpose and it self-terminates (timeout/MutationObserver on #root -> destroySplash, sessionStorage guard), but it is broader DOM control than the plugin's own overlay and could in principle mask host warnings shown in that card during the first seconds.
- lowArt route 404 body echoes the raw readFileSync error message
index.js:110If art.webp becomes unreadable (deleted, moved, permission change) after registration, any HTTP client that can reach the local webserver receives the raw Node fs error text, which typically contains the absolute path of the plugin directory — a minor local path disclosure. No attacker-controlled input is used to build the response, and there is no path traversal because the served file path is fixed at apply() time.
Static 'critical' refuted: new Function() evaluates only a build-time constant; the plugin hides the host boot card ~4s and paints a splash. No attacker input, no exfiltration, no backdoor.
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-29 · activity: Stable
• Repo created: 2026-09-29
• Stars: ★ 2 · 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 @52baihehhh-ai/dsh-splash-screen?
@52baihehhh-ai/dsh-splash-screen 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 @52baihehhh-ai/dsh-splash-screen?
Run dsh plugin --profile web add github:52baihehhh-ai/dsh-splash-screen#v1.0.0 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-14 (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.