Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin bringing the TIC-80 fantasy console to DeepSeek Harness with LLM-driven code, music, map and sprite generation plus native and live web execution.
- Full TIC-80 fantasy console capabilities inside dsh
- Conversational LLM generation of code, music, maps and sprites
- Runs natively and live in the web browser
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:NoodleStormno/dsh-plugin-tic80#v1.0.0Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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.1-rc.3 current | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v1.0.0 | ○ | ○ | ○ | ○ | ○ |
v1.0.0github○ 10 ecosystem plugin2026-10-26
https://github.com/NoodleStormno/dsh-plugin-tic80
○dsh 0.2.1-rc.3current2026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
not present in web-profile loader inventory
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
not present in web-profile loader inventory
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-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
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-14Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-14 · expires: 2026-09-21
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/NoodleStormno/dsh-plugin-tic80#v1.0.0
ID: dsh-plugin-tic80@v1.0.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
not present in web-profile loader inventory
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-plugin-tic80/?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 medium (authoritative when present) → overall medium.
v1.0.0v1.0.0git2026-10-29v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- criticalshellExec · shell
src/runner/native-runner.ts:50const found = execSync(whichCmd, { stdio: 'pipe' }).toString().trim().split(/\r?\n/)[0]; - warningfsWrite · files
src/runner/exporter.ts:34await fs.writeFile(luaPath, cart.toText(), 'utf8'); - warningfsWrite · files
src/runner/exporter.ts:40await fs.writeFile(ticPath, cart.toBinary()); - warningfsWrite · files
src/runner/exporter.ts:48await fs.writeFile(htmlPath, htmlContent, 'utf8'); - warningchildProcess · code-exec
src/runner/native-runner.ts:108proc = spawn(exePath, args, { - warningfsWrite · files
src/runner/native-runner.ts:81fs.writeFileSync(tempTicPath, cart.toBinary());
show 4 audit findings
- mediumUnsanitised options.filename is used directly as the export file name, allowing path traversal
src/runner/exporter.ts:29cart.metadata.title is sanitised, but the caller-supplied options.filename is not: a value such as '../../evil' escapes options.outputDir and writes attacker-named .lua/.tic/.html files anywhere the process can write (dropping a .lua into an auto-loaded/startup directory is the realistic worst case). Reachability depends on src/tools/index.ts, which was not provided.
- mediumTIC-80 executable is auto-discovered from CWD and hard-coded user-writable paths, then spawned
src/runner/native-runner.ts:37No integrity check precedes spawn(exePath, args). Any file named tic80.exe present in the agent's current working directory (e.g. a cloned repository) or in the developer Downloads folder is executed as the emulator, turning a data file into process execution outside the TIC-80 sandbox.
- lowCaller-supplied command strings are concatenated into the TIC-80 --cmd console line with ' & '
src/runner/native-runner.ts:100A '&' inside a caller-controlled command lets an extra TIC-80 console command (load/save/export/run) be injected. TIC-80 confines file access to --fs=<cartDir>, so the blast radius is the cartridge directory, but it still allows unintended file writes/loads inside that directory.
- lowOptional Web Live Studio listener is started from plugin config; its serving code was not provided for review
src/index.ts:57When autoRun is enabled, an HTTP/WebSocket server publishes and accepts cartridges on a fixed port. src/runner/web-runner.ts was not harvested, so authentication, origin checks and bind address of that listener cannot be verified; the shipped configs default to autoRun: false, so this is opt-in.
No critical/high issue in the reviewed files; medium risks are an unsanitised export filename (path traversal) and executing a planted tic80.exe found via CWD/hard-coded paths.
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-17 · activity: Stable
• Repo created: 2026-09-14
• 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 dsh-plugin-tic80?
dsh-plugin-tic80 is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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-plugin-tic80?
Run dsh plugin --profile web add github:NoodleStormno/dsh-plugin-tic80#v1.0.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-10-29 (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.