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
Feishu (Lark) integration plugin for DSH: scan QR to create/authorize bots and manage listeners from web panel.
- Scan QR to create Feishu bot in ~30-60s
- Auto-completes app creation, permissions, event subscription
- Optional user identity authorization for calendar/docs/mail
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 dsh-plugin-larkInstall method: npm · 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.
9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-11 · 9 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-02 → 11-11 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-19 → 11-15 · 76 points
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
08-19 → 11-16 · 77 points
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
○ The author declares no dsh version requirement — install is not blocked by version.
| 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 |
|---|---|---|---|---|---|
| 0.1.0 | ○ | ○ | ○ | ○ | ○ |
0.1.0npm○ 19 ecosystem plugin2026-11-16
dsh-plugin-lark
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-07 · expires: 2026-11-14
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-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.1.7-rc.12026-09-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-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.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
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.1.2-rc.12026-09-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-plugin-lark@0.1.0
ID: dsh-plugin-lark@0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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-plugin-lark/?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 high (authoritative when present) → overall high.
v0.1.0dsh manifest0.1.0npm2026-11-170.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
lib/index.js:149const child = spawn(LARK_CLI, ["auth", "login", "--device-code", deviceCode, "--json"], { - warningchildProcess · code-exec
lib/index.js:229const child = spawn(LARK_CLI, ["config", "init", "--app-id", appId, "--app-secret-stdin", "--brand", "feishu"], { - warningchildProcess · code-exec
lib/index.js:281const child = spawn("npx", args, { stdio: ["ignore", "pipe", "pipe"] }); - warningshellExec · shell
lib/index.js:194const out = execFileSync("/usr/bin/pgrep", ["-P", String(pid)], { timeout: 5000 }); - warningfsWrite · files
lib/index.js:430fs.writeFileSync(AUTH_STATE_FILE, JSON.stringify({ deviceCode, verificationUrl, expiresIn, at: Date.now() }, null, 2)); - warningshellExec · shell
lib/patch-bootstrap.js:32execFileSync("npx", ["--yes", "feishu-bot-bootstrap", "--help"], { timeout: 180000, stdio: "ignore" }); - warningfsWrite · files
lib/patch-bootstrap.js:111" await fs.writeFile(spec.output.artifactsDir + '/workspace-fail.txt', String(text).slice(0, 20000));\n" +
show 4 audit findings
- highBridge runs any inbound Feishu message as a full-privilege headless DSH task with no sender/chat allowlist
bridge/lark_bridge.py:107handle_message only checks that content is non-empty and that a message_id exists; sender_id/chat_id are logged but never used for authorization. Any Feishu user who can open a chat with the bot (tenant-wide by default app visibility) can send text that is executed by the local agent with the user's OS privileges and whose output is posted back to that attacker's chat — remote task/command execution and local data exfiltration.
- mediumUnpinned 'npx --yes feishu-bot-bootstrap' is downloaded and executed at runtime with user privileges
lib/index.js:281No version or integrity pin: whatever latest version of the third-party npm package (a Playwright browser automation that handles LMS console login) is published at run time gets fetched and executed on the user's machine, and patch-bootstrap.js additionally runs 'npx --yes feishu-bot-bootstrap --help'. A compromised or hijacked upstream release executes arbitrary code without user review; the audit-time code is not necessarily the code that runs.
- lowPlugin silently rewrites third-party package code inside the shared npx cache without integrity verification
lib/patch-bootstrap.js:173The plugin picks the first ~/.npm/_npx/*/node_modules/feishu-bot-bootstrap directory it finds and overwrites its dist/flow.js with string substitutions, leaving the npm-cached package permanently modified for every later npx run. It mutates code outside its own install path, breaks cache integrity assumptions, and any pre-existing tampered directory in that cache would be selected and executed.
- lowOAuth device_code persisted in plaintext and echoed back in the HTTP response
lib/index.js:430The short-lived device code returned by lark-cli is stored unencrypted in ~/.dsh/lark-connector/auth-state.json (default umask) and returned to the browser although the client only needs qrUrl; anyone able to read that file or an intercepted response gains a usable polling credential for the pending authorization.
Lark bridge executes any inbound Feishu message as a headless DSH task with no sender allowlist, and the plugin auto-runs an unpinned npx package it silently patches.
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-08-30 · activity: Stable
• Repo created: 2026-08-16
• 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 dsh-plugin-lark?
dsh-plugin-lark 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 dsh-plugin-lark?
Run dsh plugin --profile web add dsh-plugin-lark 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-17 (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.
