Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Saves Markdown, HTML, or plain text as Feishu cloud docx documents via official OpenAPI with OAuth user identity and full-fidelity formatting.
- Converts Markdown / HTML / plain text into Feishu docx
- Full fidelity: real tables, code blocks, images, LaTeX, nested lists
- Creates docs as your OAuth user in a DSH folder with smart naming and retries
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:tttwh/dsh-feishu-doc-saver#v1.0.1Install method: GitHub · runtime test inconclusive (L5 unknown)
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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-02 → 11-05 · 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-07 → 11-05 · 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 plugin
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.0.1 | ○ | ○ | ○ | ○ | ○ |
v1.0.1github○ 9 ecosystem plugin2026-11-15
https://github.com/tttwh/dsh-feishu-doc-saver
○dsh 0.2.2-rc.3current2026-11-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
not present in web-profile loader inventory
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-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
not present in web-profile loader inventory
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
not present in web-profile loader inventory
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-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
not present in web-profile loader inventory
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-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-03Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/tttwh/dsh-feishu-doc-saver#v1.0.1
ID: dsh-feishu-doc-saver@v1.0.1@dshunknown · profile: l3-fullscan
Issued: 2026-10-03 · expires: 2026-10-10
View checks & evidence
not present in web-profile loader inventory
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-feishu-doc-saver/?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 medium (authoritative when present) → overall medium.
—v1.0.1git2026-11-16v1.0.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcessImport · code-exec
feishu-oauth.mjs:12import { spawn } from 'node:child_process' - warningnetIp · network
feishu-oauth.mjs:15const REDIRECT = `http://127.0.0.1:${PORT}/feishu-oauth/callback` - warningnetIp · network
feishu-oauth.mjs:79const u = new URL(req.url, `http://127.0.0.1:${PORT}`) - warningnetIp · network
feishu-oauth.mjs:169console.log(`本地回调服务已启动: http://127.0.0.1:${PORT}`) - warningfsWrite · files
feishu-oauth.mjs:144fs.writeFileSync(p, JSON.stringify(record, null, 2), { mode: 0o600 }) - warningmanifest-fs-unfenced · sandbox
agent.cordis.ymlMutating filesystem tool has no explicit fs backend in realm - warningmanifest-search-unfenced · sandbox
agent.cordis.ymlSearch tool reads without an explicit fs mount - warningmanifest-shell-unfenced · sandbox
agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 5 audit findings
- mediumImage src from document content is passed unsanitised to curl (arbitrary local file read / SSRF)
saver-plugin.mjs:309Image references are extracted from the Markdown/HTML passed as `content` (extractImages, regex /!\[[^\]]*\]\(([^)\s]+).../). For non-http sources the raw string becomes the path handed to uploadImage, which runs curl with '-F', 'file=@' + filePath (line 280) — this read does not go through the sandboxed fs service, so `` or `` causes an arbitrary local file to be uploaded off-machine to Feishu. For http(s) sources, downloadTo (line 270) fetches any URL with -L (redirects followed) and no host allowlist, allowing requests to loopba
- mediumToken refresh rewrites credentials with danger-full-access to a hard-coded foreign workspace path
saver-plugin.mjs:115persistTokens is called on every token refresh and writes the full record (app_id, app_secret, access_token, refresh_token) to every candidate path, requesting the sandbox mode 'danger-full-access' for absolute paths and a hard-coded author-machine workspaceRoot. `.feishu/feishu-user-tokens.json` (relative, line 37) means long-lived refresh tokens plus the app secret can be written into the working directory, i.e. potentially into a git repository or shared folder, and the write is not given an explicit 0600 file mode (unlike the oauth script).
- lowHard-coded developer-specific absolute token fallback path
feishu-oauth.mjs:19If ~/.dsh is unwritable, the script tries to write the credential JSON (including app_secret) into a hard-coded path belonging to the author's machine; on any other host this is either a silent failure or an unintended directory creation outside the user's control, and it leaks the author's local layout.
- lowOAuth callback never verifies the state parameter (CSRF, mitigated by PKCE)
feishu-oauth.mjs:84state is generated and appended to the authorize URL (line 59/65) but the /feishu-oauth/callback handler only reads code/error and never compares the returned state, so any page able to reach 127.0.0.1:3089 can deliver a code to the listener. Impact is limited because the same server binds the code to its own PKCE code_verifier, so a foreign code cannot be exchanged; residual risk is a wasted/failed authorization rather than account binding.
- lowTool description instructs the agent to proactively upload every document to Feishu
saver-plugin.mjs:406The registered tool description contains an imperative addressed to the model rather than a capability description. It biases the agent toward automatically uploading freshly written documents (which may contain sensitive local content) to a third-party cloud service without an explicit user request each time.
No code execution or backdoor; medium risks: image paths/URLs from content are passed unvalidated to curl (local file read + SSRF) and refreshed tokens are written with danger-full-access to a hard-coded path.
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-02 · activity: Stable
• Repo created: 2026-10-02
• Stars: ★ 0 · 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 @tttwh/dsh-feishu-doc-saver?
@tttwh/dsh-feishu-doc-saver is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @tttwh/dsh-feishu-doc-saver?
Run dsh plugin --profile web add github:tttwh/dsh-feishu-doc-saver#v1.0.1 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-16 (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.
