Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Desktop AI agent with a Galgame-style visual novel interface, wrapping Claude Code CLI for an immersive experience.
- 110+ PNG character expressions with dynamic positioning
- 6 Japanese-style backgrounds with smooth transitions
- 30+ BGM tracks from the visual novel
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
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
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), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-07 · 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
09-24 → 10-17 · 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◼ Ecosystem app
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
| plugin \ dsh | dsh 0.2.2-alpha.2 | dsh 0.2.1-alpha.2 |
|---|---|---|
| v1.6.7-dsh | · | · |
v1.6.7-dshgithub2026-11-14
https://github.com/liebaojun/MakoCode
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
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/makocode/?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.6.7-dshv1.6.7-dshgit2026-11-15v1.6.7-dshsame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningfsWrite · files
assets/extract-xp3.js:146fs.writeFileSync(outPath, file.data); - warningnetIp · network
dsh-engine.js:290async function initDshEngine({ baseUrl = 'http://127.0.0.1:3100', log = () => {} } = {}) { - warningchildProcess · code-exec
electron-main.js:80spawnSync('taskkill', ['/PID', String(serverProc.pid), '/F', '/T'], { stdio: 'pipe' }); - warningchildProcess · code-exec
electron-main.js:92const result = spawnSync('cmd.exe', [ - warningchildProcess · code-exec
electron-main.js:115const r = spawnSync('cmd.exe', ['/d', '/c', - warningnetIp · network
electron-main.js:57const MAIN_URL = `http://127.0.0.1:${SERVER_PORT}`; - warningfsWrite · files
electron-main.js:148const dshLog = fs.createWriteStream(path.join(app.getPath('userData'), 'dsh.log'), { flags: 'a' }); - warningfsWrite · files
electron-main.js:268const serverLog = fs.createWriteStream(path.join(app.getPath('userData'), 'server.log'), { flags: 'a' }); - warningfsWrite · files
electron-main.js:747fs.writeFileSync(personaFile, persona, 'utf8'); - warningnetIp · network
lib/constants.js:33DSH_BASE_URL: "http://127.0.0.1:3100", - warningfsWrite · files
lib/galgame-features.js:63try { fs.writeFileSync(path.join(appDir, TASKS_FILE), JSON.stringify(tasks, null, 2), 'utf8'); } catch {} - warningfsWrite · files
lib/galgame-features.js:276fs.writeFile(fp, JSON.stringify(save, null, 2), "utf8", (err2) => {
show 3 audit findings
- highExpression-delete API uses unvalidated fileName -> arbitrary file deletion (path traversal)
lib/galgame-features.js:830handleUserCharaExpressionDelete takes fileName straight from the JSON body, while only folderName is sanitized. A client that can reach the loopback API can first create a character (handleUserCharaCreate returns an attacker-visible folderName) and then POST fileName:"../../../../..." to unlink any file the process user can write, inside or outside the app directory. This is an unrestricted filesystem-delete primitive on attacker-controlled input; no auth/origin check is present in the handler itself (server.js was not harvested, so routing-level protection cannot be confirmed).
- highXP3 extractor zip-slip: archive-controlled names are written outside the output directory
assets/extract-xp3.js:140File names parsed from the .xp3 archive are used verbatim in path.join(outputDir, file.name); the only transformation turns backslashes into forward slashes, which converts Windows-style '..\..\' traversal into working '/../' traversal. Extracting a crafted archive (a normal use of this shipped CLI tool) yields arbitrary file write with attacker-controlled content, e.g. overwriting scripts or config files of the user's account.
- lowmacOS Node.js bootstrap downloads and unpacks a binary without integrity verification
lib/installer.js:83installMacNode fetches the version list and the tarball over HTTPS and extracts it into the app data directory, whose bin is later prepended to PATH (electron-main.js). No SHASUMS256 verification is performed, so integrity depends solely on TLS and on nodejs.org/redirect targets; a compromised or spoofed download becomes the Node runtime used by the app.
Two high-severity path-traversal bugs: the character-expression delete API can unlink arbitrary files, and the XP3 extractor writes archive entries outside the output directory.
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-08-14 · activity: Inactive
• Repo created: 2026-06-16
• Stars: ★ 158 · Forks: 7
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/liebaojun/MakoCode
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 MakoCode?
MakoCode is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.
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 MakoCode?
This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.
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-15 (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.
