Read-only work reports for DeepSeek Harness: reconstruct what an agent task actually did from session logs — tools used, files read/written, commands run, test results, failures, token usage, and whether it finished. Fully offline, no API key, no data leaves your machine.
Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Read-only reports that reconstruct what an agent task actually did from session logs, without any API key or network access.
- Reconstructs tools used, files read/written and commands run
- Surfaces test results, failures and token usage per task
- Fully offline and read-only, no data leaves your machine
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.
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); the npm pair from every snapshot.
current (registry 2026-11-11) · 6 samples (roughly every 7 days), 1 of them reconstructed (hollow dots); sampled points, not a daily series
10-06 → 11-07 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-17 → 11-07 · 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
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:Neo65536-engineer/dsh-agent-log#v0.4.0Install 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.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v0.4.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.4.0github✓ 10 runtime-verified2026-11-05
https://github.com/Neo65536-engineer/dsh-agent-log
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@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.
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@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.
✓dsh 0.2.1-alpha.42026-10-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
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-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.1.7-rc.22026-09-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Neo65536-engineer/dsh-agent-log#v0.4.0
ID: dsh-agent-log@v0.4.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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-agent-log/?ref=badge)``[](https://www.dsh.so/artifact/dsh-agent-log/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-log/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-log/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-log/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-log/?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 low (authoritative when present) → overall low.
v0.4.0dsh manifestv0.4.0git2026-11-11v0.4.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalshellExec · shell
bin/verify-compose.mjs:88return execSync('where dsh', { encoding: 'utf8' }).trim().split('\n')[0].trim() - criticalshellExec · shell
bin/verify-compose.mjs:128execSync(`cmd /c mklink /J "${join(TMP, 'node_modules')}" "${srcModules}"`, { stdio: 'ignore' }) - criticalshellExec · shell
bin/verify-compose.mjs:140out = execSync(`"${dsh}" --profile ${TMP_NAME} --dump-config`, {
show 2 audit findings
- lowDev verification script builds Windows shell commands by string interpolation of env/filesystem paths
bin/verify-compose.mjs:128DSH_HOME (from --home/$DSH_HOME/$DSH_PROFILE_DIR) and the profile directory name (read from readdirSync) are interpolated into a `cmd /c` command line, and the dsh CLI path is likewise interpolated into a second execSync. A value containing a quote or shell metacharacter would break out of the quoting and run an extra command as the invoking user. Reachability is low: the script is a manual developer helper (`npm run compose`), not part of the plugin runtime, and the inputs come from the same user's own environment and DSH home rather than across a trust boundary.
- lowRecursive rmSync on the dev link path that may hold a junction
bin/dev-setup.mjs:111If symlinkSync throws after (or while) creating a junction/symlink at node_modules/@deepseek-ai, the catch block recursively removes that path. Node normally unlinks the link itself, but recursive delete of a reparse point is platform-sensitive and, in the worst case, could touch the linked host directory (the real DSH @deepseek-ai runtime). The preceding existsSync(linkPath) guard ensures the path did not pre-exist, so exposure is limited to a partially created link.
The 3 critical static-scan hits appear to be heuristic flags on child_process/fs usage inside dev-only verification scripts; no critical or high risk is reachable, but index.js and core/* were not harvested.
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-26 · activity: Stable
• Repo created: 2026-09-26
• 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 @Neo65536-engineer/dsh-agent-log?
@Neo65536-engineer/dsh-agent-log 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 @Neo65536-engineer/dsh-agent-log?
Run dsh plugin --profile web add github:Neo65536-engineer/dsh-agent-log#v0.4.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (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-11 (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.