Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Web plugin to recall and cycle sent messages with Ctrl+Up/Down like a terminal, no core changes.
- Recall sent messages with Ctrl+Up/Ctrl+Down
- Compatible with DSH snapshots 0808-0812
- Browser-side implementation, zero core changes
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:lhh010/dsh-input-history#v0.1.34Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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) · 8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 8 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-13 · 6 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.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.36 | · | · | · | · | · |
| v0.1.34 | ✓ | · | · | · | · |
| v0.1.32 | · | · | · | · | · |
| v0.1.30 | · | ✓ | ✓ | · | · |
| v0.1.28 | · | · | · | ✓ | · |
v0.1.36github2026-11-20
https://github.com/lhh010/dsh-input-history
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.1.34github✓ 1 runtime-verified2026-11-15
https://github.com/lhh010/dsh-input-history
✓dsh 0.2.2-rc.32026-11-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/lhh010/dsh-input-history#v0.1.34
ID: dsh-input-history@v0.1.34@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.32github2026-11-13
https://github.com/lhh010/dsh-input-history
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.1.30github✓ 2 runtime-verified2026-11-06
https://github.com/lhh010/dsh-input-history
✓dsh 0.2.2-rc.12026-11-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/lhh010/dsh-input-history#v0.1.30
ID: dsh-input-history@v0.1.30@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/lhh010/dsh-input-history#v0.1.30
ID: dsh-input-history@v0.1.30@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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.
v0.1.28github✓ 1 runtime-verified2026-10-27
https://github.com/lhh010/dsh-input-history
✓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/lhh010/dsh-input-history#v0.1.28
ID: dsh-input-history@v0.1.28@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-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.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
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-input-history/?ref=badge)``[](https://www.dsh.so/artifact/dsh-input-history/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-input-history/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-input-history/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-input-history/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-input-history/?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.1.36dsh manifestv0.1.36git2026-11-21v0.1.36same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
lib/index.js:195const child = spawn("pnpm", ["add", `${PACKAGE_SPEC}@github:${MIRROR}#${tag}`], { - warningshellExec · shell
lib/index.js:91execFile("git", [ - warningshellExec · shell
src/update-endpoint.ts:41execFile('git', ['ls-remote', '--tags', REPO_GIT], { encoding: 'utf8', maxBuffer: 1024 * 1024, timeout: GIT_TIMEOUT_MS, killSignal: 'SIGKILL - warningshellExec · shell
sync-mirrors.mjs:29const git = (...args) => execFileSync('git', args, { stdio: ['ignore', 'inherit', 'inherit'] }) - warningshellExec · shell
sync-mirrors.mjs:30const gitOut = (...args) => execFileSync('git', args, { encoding: 'utf8' })
show 4 audit findings
- mediumSelf-update installs its own package from a mutable git tag with no integrity verification
src/update-endpoint.ts:129The tag is only shape-checked (/^v\d+\.\d+\.\d+$/), not pinned to a commit or hash, so whatever the upstream repo `lhh010/dsh-input-history` currently serves at that ref is installed and its build/install scripts run on the user's machine. A compromised upstream account (or a moved tag) yields code execution on every click. This is inherent to self-update but is unmitigated here (no sha/provenance check, no signature).
- lowUpdate route guarded only by a public constant header and an Origin check that accepts a missing Origin
src/update-endpoint.ts:188``x-dsh-plugin-update: click`` is a documented literal in the shipped client, not a secret, and a request without an Origin header passes the same-origin test. Any local process (or a browser page that succeeds in a non-CORS request path) able to reach the profile port can trigger a package install/modification of ~/.dsh/profiles/web without user interaction. Browser CSRF is mostly blocked by the custom header forcing a preflight, so impact is limited to local/loopback attackers.
- lowUnauthenticated GET /latest performs outbound git/HTTPS calls and exposes runtime version data
src/update-endpoint.ts:41Each cache miss (60s TTL) spawns a git process and an HTTPS fetch to third-party hosts, disclosing the user's IP to GitHub and answering with the exact installed DSH version and plugin version to any caller of the route. Values are hard-coded and timeouts are enforced, so this is fingerprinting/minor resource use rather than a compromise.
- lowClipboard remediation prompt instructs running `pnpm approve-builds --all`
src/client/update-check.ts:93On update failure the plugin writes an instruction block to the clipboard that a user or an AI agent may execute verbatim; it tells them to blanket-approve every dependency build script, disabling pnpm's install-script guard for the whole profile — a privilege widening beyond what this plugin needs.
Small UI plugin; its host half adds a header-gated self-update route that runs `pnpm add` of its own mutable GitHub tag with no integrity check — real supply-chain surface.
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-18 · activity: Active
• Repo created: 2026-08-13
• Stars: ★ 3 · Forks: 1
• 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-input-history?
dsh-input-history 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-input-history?
Run dsh plugin --profile web add github:lhh010/dsh-input-history#v0.1.36 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus runtime verification (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-21 (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.
