Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Floor-triggered session compaction for DeepSeek Harness: compact old history once M real user floors accumulate, keeping the newest N verbatim
Installation
dsh plugin --profile web add github:MengXinSu/floor-limiterInstall method: GitHub · runtime verified (L5)
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.1-rc.2 current |
|---|---|
| 13c4b8 | ✓ |
13c4b8github✓ 1 runtime-verified2026-10-19
https://github.com/MengXinSu/floor-limiter
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/MengXinSu/floor-limiter (version unstated)
ID: floor-limiter@13c4b8@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/floor-limiter/)``[](https://www.dsh.so/artifact/floor-limiter/)`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 — stricter wins → overall low.
v0.1.4dsh manifest0.1.4git2026-10-210.1.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalnewFunction · code-exec
lib/index.js:412schema.callback = new Function("return " + schema.callback)();
show 2 audit findings
- lowDiagnostic log writes session ID suffix and engine error text to a home-directory file
src/index.ts:70On mount, on the first pre-step crossing the trigger, and on compaction failure, `diag()` appends `sessionId` (last 8 chars of `session.id`) and `outcome.reason` (raw compaction-engine error, truncated to 180 chars) to a fixed file in the user's home directory (line 72: `appendFileSync(file, ...)`). The path is overridable via the `DSH_FLOOR_LIMITER_LOG` environment variable and the file is created with default umask permissions. No conversation text is deliberately logged, but engine error messages may embed content, and raw newlines in `reason` can forge extra log lines. Impact is limited to
- lowVendored schemastery bundle contains new Function on string schema.callback (unreachable here)
lib/index.js:412The shipped bundle inlines cosmokit/schemastery, whose `Schema()` constructor evaluates a string `callback` with `new Function`. This is a code-execution primitive, but the floor-limiter schema (src/settings.ts) only builds `object/boolean/number` schemas with `default/min/step/volatile` and never passes a string callback or `refs`; `Schema.resolve` used on config does not construct schemas. The path is therefore dead code in this plugin, carried only because the build bundles its dependency.
Host plugin only counts user floors and calls the official compaction seam; bundled `new Function` in vendored schemastery is unreachable and only a local diagnostic log is written.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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: Active
• Repo created: 2026-09-03
• 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).
