Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
配合官方wps365-cli的dsh插件
Installation
dsh plugin --profile web add @tryao/dsh-wps365-pluginInstall method: npm · 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 |
|---|---|
| 0.2.0 | ✓ |
| v0.1.4 | · |
0.2.0npm✓ 1 runtime-verified2026-10-21
@tryao/dsh-wps365-plugin
✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @tryao/dsh-wps365-plugin@0.2.0
ID: dsh-wps365-plugin@0.2.0@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
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.
v0.1.4github2026-10-18
https://github.com/YiuTerran/dsh-wps365-plugin
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-wps365-plugin/)``[](https://www.dsh.so/artifact/dsh-wps365-plugin/)`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.2dsh manifest0.2.2npm2026-10-210.2.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalpipeShell · shell
src/skill-catalog.js:196: '`curl -fsSL https://open-docs.wpscdn.cn/cli/install.sh | bash`' - warningshellExec · shell
assets/wps365-docs/scripts/xlsx_edit.py:237exec(compile(code, py_file, "exec"), env) # noqa: S102 本地可信脚本
show 4 audit findings
- mediumxlsx_edit.py exec()s arbitrary Python from a runtime-supplied --py path
assets/wps365-docs/scripts/xlsx_edit.py:234The path comes from the agent's --py argument, and any file it is persuaded to pass (for example by instructions embedded in a cloud document it just fetched) is executed as the user with the WPS 365 CLI and its delegated token reachable via subprocess. The inline `本地可信脚本` comment is an assertion, not a control, and nothing restricts the path to a work directory.
- mediumAttachment file name built from document-controlled sourceKey allows path traversal on image download
assets/wps365-docs/scripts/otl_fetch.py:119`key` is `attrs.sourceKey` taken straight from the exported .otl model, and the download URL is looked up by that same key, so a document crafted by an attacker can carry both. A key containing `../` sequences makes the downloaded bytes land outside `<out>/img` (extension forced by magic bytes to .png/.jpg/.webp/.gif/.bin), giving a limited arbitrary-path file write when a user asks the agent to read such a document.
- lowInjected skill hint tells the model to pipe a remote installer into the shell
src/skill-catalog.js:193When wps365-cli is not found, buildRuntimeHint appends this text to the skill body, so the model is instructed to fetch and execute a remote script with no integrity check. Compromise or misconfiguration of that host turns every such session into code execution on the user's machine.
- lowLibreOffice kit lookup runs the first node/cli.js matched by glob without integrity check
assets/wps365-docs/scripts/xlsx_edit.py:152Search roots include DSH_APP_ROOT / DSH_RESOURCES, ~/.dsh/dsh-runtimes/* and ancestors of the script directory (in a checkout, the repo root). Whatever `dependencies/node/bin/node` (or `app.asar.unpacked/.../cli.js`) glob matches first is executed; there is no ownership or signature check, so a writable directory in the search set can supply the binary that gets run.
Plugin only registers a bundled skill; residual risk is in the shipped Python helpers (exec of --py, attachment path traversal) and a pipe-to-shell install hint.
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-21 · activity: Active
• Repo created: 2026-10-13
• 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).