Feishu/Lark bridge for DeepSeek Harness: scan-to-connect PersonalAgent binding, streaming cards, git-worktree project workspaces, parallel per-scope tasks, multi-role agents, cross-session notify, in-chat model/key management, and a safety-net guardian that still answers in Feishu after dsh crashes.
Author: PlutoKeating · Notifications & Integrations · Catalog snapshot: 2026-09-19Canonical semantic path
Feishu/Lark bridge for DeepSeek Harness: scan-to-connect PersonalAgent binding, streaming cards, git-worktree project workspaces, parallel per-scope tasks, multi-role agents, cross-session notify, in-chat model/key management, and a safety-net guardian that still answers in Feishu after dsh crashes.
Imported third-party catalog description; not a Registry verification conclusion.39 stars · 7317 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 39 stars, 565 commits, 5 forks, and 1 watches; latest commit 2026-08-25.
Conclusion: Resolved npm release 0.19.16, published 2026-08-25, license AGPL-3.0.
Conclusion: Compatibility verification did not pass: the DSH process exited because the plugin imports an API that this DSH version does not export. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 5 code capabilities: contains credential or token handling code, may read environment variables, may create or modify files, may access the network, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-lark-bot@0.19.16; SHA-256: 924ca66bb8561f2cf6d8201d94fa5586330a06fafb1df84ccb5ea5afdf6c78ef.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-lark-bot. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-lark-botAnalyzed 0.19.16github:PlutoKeating/dsh-lark-botExact version not resolved