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
A general pluggable coding agent built on DeepSeek-Harness, preserving plugin architecture and providing a Web UI.
- Source-first downstream of DeepSeek Harness
- Cordis-powered 'everything is a plugin' architecture
- Quick start from new machine to Web UI response
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.
current (registry 2026-11-17) · 7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-11 · 7 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-01 → 11-11 · 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◼ 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-rc.3 current | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| vm-assets-v1 | · | · | · | · | · |
| harniverse-v1.0.0-rc.1 | · | · | · | · | · |
| c86e7a | ◼ | ◼ | ◼ | ◼ | ◼ |
| 1e814f | · | · | · | · | · |
vm-assets-v1github2026-11-14
https://github.com/KeepLost/harniverse
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
harniverse-v1.0.0-rc.1github2026-11-13
https://github.com/KeepLost/harniverse
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
c86e7agithub◼ 20 ecosystem app2026-11-16
https://github.com/KeepLost/harniverse
◼dsh 0.2.2-rc.3current2026-11-16Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.2.2-alpha.22026-11-03Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-03 · expires: 2026-11-10
View checks & evidence
This level was not executed in this scan.
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-02Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-02 · expires: 2026-11-09
View checks & evidence
This level was not executed in this scan.
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-30Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
This level was not executed in this scan.
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 app
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
This level was not executed in this scan.
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-14Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
This level was not executed in this scan.
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-08Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
This level was not executed in this scan.
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-29Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
This level was not executed in this scan.
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-28Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-28 · expires: 2026-10-05
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.7-rc.12026-09-23Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.7-alpha.22026-09-23Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.7-alpha.12026-09-22Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.1
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.7-alpha.1 · profile: l4-sandbox
Issued: 2026-09-22 · expires: 2026-09-29
View checks & evidence
This level was not executed in this scan.
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-21Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
View checks & evidence
This level was not executed in this scan.
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-16Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
This level was not executed in this scan.
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-11Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.3-alpha.22026-09-10Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.3-alpha.2 · profile: l3-fullscan
Issued: 2026-09-10 · expires: 2026-09-17
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.3-alpha.12026-09-06Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.2-rc.12026-09-04Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: artifact unstated (historical)
ID: harniverse@c86e7a@dsh0.1.2-rc.1 · profile: l4-sandbox
Issued: 2026-09-04 · expires: 2026-09-11
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼dsh 0.1.2-alpha.12026-09-02Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: harniverse@c86e7a@dsh0.1.2-alpha.1 · profile: l4-sandbox
Issued: 2026-09-02 · expires: 2026-09-09
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
◼prehistory2026-10-05Ecosystem app
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/KeepLost/harniverse (version unstated)
ID: harniverse@c86e7a@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1e814fgithub2026-08-28
https://github.com/KeepLost/harniverse
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
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/harniverse/?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 low (authoritative when present) → overall low.
v1.0.0-rc.3vm-assets-v1git2026-11-17vm-assets-v1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningmanifest-fs-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/code/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-fs-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/cordis/agent.cordis.ymlShell tool without a sandbox runner or policy in realm - warningmanifest-fs-unfenced · sandbox
apps/cli/config/agent-presets/minimal/agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-shell-unfenced · sandbox
apps/cli/config/agent-presets/minimal/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
The artifact has changed (audited git e6a1a11d540f2d9555e9a9578e3d6612223699b5 → current git 768a065bc6cfe114e1530b3a920d06ea0ef6c48a): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.
show 3 audit findings
- low`!!js` YAML tags evaluate embedded JavaScript in the host process when a cordis bundle is loaded
packages/bundle/base/cordis.patch.ymlThe config loader evaluates `!!js` expressions with full host privileges. Every expression in the harvested bundles is a static first-party literal over process.env, so nothing here is attacker-controlled; the residual risk is that the same loader will evaluate any expression present in a user or third-party profile patch layer (the headless bundle comment notes user patch layers stay live), turning a writable profile file into code execution at startup.
- lowOpt-in telemetry row uploads unredacted session log records to a vendor OTLP endpoint
packages/bundle/base/cordis.patch.ymlIf a deployment sets DSH_TELEMETRY_MODE, raw session-log records (per the adjacent comment, with no redaction rule) are POSTed to a remote collector, including conversation content and the anonymous user id. It is default-DISABLED and documented in the same file, and DSH_TELEMETRY_DISABLED opts out, so this is an explicitly-enabled capability rather than a covert channel.
- lowExample ACP composition switches sandbox to danger-full-access and approval to 'never' when DSH_SNAPSHOT is set
examples/acp-agent/cordis.yml:30Under the snapshot harness the bash and filesystem tools run with no sandbox confinement and the user-approval policy resolves to 'never', so any model-issued command executes unguarded. This only applies to the example/demo app config used by the test harness (DSH_SNAPSHOT), not to the shipped base profile, which keeps workspace-write with 'ask'.
Harvested files are declarative dsh bundle YAML, package.json, and type-only stubs; no plugin runtime logic, static-scan warnings refuted (risk stays low).
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-16 · activity: Active
• Repo created: 2026-08-14
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/KeepLost/harniverse
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 harniverse?
harniverse 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 harniverse?
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-17 (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.
