Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it does
DSH web plugin: one-click Approve & escalate on the approval card — approves the pending request and switches the live session to a permission preset
Installation
dsh plugin --profile web add github:almazom/dsh-almazom-approve-escalateInstall 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.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 |
|---|---|---|---|---|---|
| 7cd850 | ✓ | ✓ | ✓ | ✓ | ✓ |
7cd850github✓ 11 runtime-verified2026-10-27
https://github.com/almazom/dsh-almazom-approve-escalate
✓dsh 0.2.1-rc.3current2026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-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.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.1.7-rc.12026-09-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-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.1.5-rc.22026-09-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-15 · expires: 2026-09-22
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/almazom/dsh-almazom-approve-escalate (version unstated)
ID: dsh-almazom-approve-escalate@7cd850@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.
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-almazom-approve-escalate/?ref=badge)``[](https://www.dsh.so/artifact/dsh-almazom-approve-escalate/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-almazom-approve-escalate/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-almazom-approve-escalate/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-almazom-approve-escalate/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-almazom-approve-escalate/?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 medium (authoritative when present) → overall medium.
v0.2.0dsh manifest0.2.0git2026-10-290.2.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalshellExec · shell
docs/e2e/approval_probe.mjs:11execSync(`mkdir -p ${SHOTS}`) - criticalshellExec · shell
docs/e2e/approval_probe.mjs:15const login = execSync( - criticalshellExec · shell
e2e/approval_probe.mjs:11execSync(`mkdir -p ${SHOTS}`) - criticalshellExec · shell
e2e/approval_probe.mjs:15const login = execSync( - warningnetIp · network
docs/e2e/approval_probe.mjs:9const BASE = 'http://127.0.0.1:39781' - warningcurlDownload · network
docs/e2e/approval_probe.mjs:16`curl -s -X POST ${BASE}/_dsh_login -d "token=${TOK}" -D - -o /dev/null`, - warningnetIp · network
e2e/approval_probe.mjs:9const BASE = 'http://127.0.0.1:39781' - warningcurlDownload · network
e2e/approval_probe.mjs:16`curl -s -X POST ${BASE}/_dsh_login -d "token=${TOK}" -D - -o /dev/null`,
show 4 audit findings
- mediumClient falls back to danger-full-access when the host config fetch fails, contradicting the configured preset
lib/client.js:43The click handler and the /yolo path read config.preset, and loadConfig()'s catch returns DEFAULT_CONFIG when the config route is unavailable (route disabled, transient failure, proxy path mismatch): 'return Object.assign({}, DEFAULT_CONFIG, { fromHost: false });'. In that state the card button silently strengthens the session from the patch-configured 'workspace-write' (cordis.patch.yml) to full access — sandbox off, no further approval prompts for the rest of the session. This is a fail-open privilege escalation driven by an availability precondition rather than the operator's configuration.
- lowA single click both answers the pending approval and switches the whole session policy, replacing the shipped approval renderer
lib/client.js:248The plugin occupies the single 'conversation.approval.detail' slot (priority -10, replacing the shipped ApprovalCommand renderer) and its action performs a session-wide policy change in addition to answering one tool call with 'allowed-once'. The consequence (sandbox off / no further prompts) is disclosed in the hint and warning text, but it expands a per-request approval into a persistent session-wide permission change for the duration of the session.
- lowPublished e2e probe interpolates a CLI argument into an execSync shell command
docs/e2e/approval_probe.mjs:16TOK comes from process.argv[2] and is interpolated unquoted into a shell command executed by execSync. This file is a developer harness that the plugin runtime never loads (the same file also exists at e2e/, outside the published 'files' list), so impact is limited to someone running the probe with a hostile argument; it is not reachable from the plugin's normal operation.
- lowEmbedded comment claims a dated 'operator order' to pre-authorize the fail-open default
lib/client.js:40A comment inside the artifact asserts external authority to legitimise the fail-open behaviour and discourage reviewers from flagging it. It is not executable and does not change runtime behaviour, but it is an attempt to steer security review rather than evidence of approval.
Disclosed approval-friction plugin; the main issue is a fail-open default that escalates sessions to danger-full-access when its config fetch fails.
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-10-15 · activity: Active
• Repo created: 2026-09-14
• 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).
Frequently asked questions
What is dsh-almazom-approve-escalate?
dsh-almazom-approve-escalate 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 dsh-almazom-approve-escalate?
Run dsh plugin --profile web add github:almazom/dsh-almazom-approve-escalate 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-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.