Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Conversational Proxmox VE management: inspect nodes, VMs, containers and storage, and run approved clone/migrate/backup operations.
- Inspect nodes, QEMU VMs, LXC containers, storage, network, firewall, cluster, Ceph
- Manage power, clone, migrate, snapshot, resize/move disks, backups, HA and replication
- Every write operation requires a native user approval prompt; credentials stay in DSH store
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
dsh plugin --profile web add github:we39/dsh-pve#v0.2.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.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| v0.2.1 | · | · | · |
| v0.2.0 | ✓ | ✓ | ✓ |
v0.2.1github2026-10-21
https://github.com/we39/dsh-pve
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.2.0github✓ 3 runtime-verified2026-10-19
https://github.com/we39/dsh-pve
✓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/we39/dsh-pve#v0.2.0
ID: dsh-pve-2@v0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/we39/dsh-pve#v0.2.0
ID: dsh-pve-2@v0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/we39/dsh-pve#v0.2.0
ID: dsh-pve-2@v0.2.0@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-pve-2@v0.2.1@dsh0.2.1-rc.2 (l3-fullscan)
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-pve-2/)``[](https://www.dsh.so/artifact/dsh-pve-2/)`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 — stricter wins → overall medium.
v0.2.1dsh manifestv0.2.1git2026-10-21v0.2.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalshellExec · shell
index.js:84- pve_vm_monitor (raw QEMU monitor), pve_vm_sendkey, pve_vm_agent exec (runs inside the guest).
show 3 audit findings
- mediumModel-accessible arbitrary command execution on the hypervisor and inside guests (approval-gated)
index.jsThe tool surface hands the model root-level execution on the PVE node (pve_node_execute), plus guest-level execution (pve_vm_agent command=exec) and raw QEMU monitor access (pve_vm_monitor). The only barrier is the native approval prompt, which shows the exact argv but is routinely approved; untrusted PVE-returned content (task logs, syslog, VM notes/config) can attempt indirect injection that funnels into one of these tools. Nothing here is exploitable without the user's click, which is why this is medium rather than high/critical.
- mediumpve_storage_upload reads any local file path and ships it to the configured PVE host
index.jsNo allowlist or path restriction: the model can name any readable path (e.g. ~/.ssh/id_rsa, DSH credential files, /etc/shadow) and the plugin will POST its bytes to the selected PVE source. Combined with model-visible untrusted PVE data, this is a local-file exfiltration primitive; the destination is user-configured and the approval text does show the path, so exploitation needs a careless approval (or a hostile/compromised configured source).
- lowPlaintext HTTP base URLs are accepted, sending API secrets/passwords without transport encryption
index.js:223If a user configures an http:// source (the settings card explicitly advertises HTTP for internal deployments), the API token secret (Authorization: PVEAPIToken user@realm!id=SECRET) or the login password posted to /access/ticket travel in cleartext and can be captured by anyone on the path. Requires a user-chosen http:// URL, hence low.
Well-gated PVE admin toolkit; residual risk is model-accessible root command execution and arbitrary local-file upload behind a mandatory approval prompt, plus cleartext HTTP support.
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-10-19 · activity: Active
• Repo created: 2026-09-10
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/we39/dsh-pve
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).