What it may solve
DeepSeek Harness 消息通知Plugin · 7 类事件 × 多渠道推送 × 路由矩阵(Server酱³/Windows Toast/企业微信/Webhook)
Imported third-party catalog description; not a Registry verification conclusion.DeepSeek Harness 消息通知Plugin · 7 类事件 × 多渠道推送 × 路由矩阵(Server酱³/Windows Toast/企业微信/Webhook)
Author: lzylyd · Notifications & Integrations · Catalog snapshot: 2026-09-19Canonical semantic path
DeepSeek Harness 消息通知Plugin · 7 类事件 × 多渠道推送 × 路由矩阵(Server酱³/Windows Toast/企业微信/Webhook)
Imported third-party catalog description; not a Registry verification conclusion.— stars · 1546 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: 0 stars, 25 commits, 0 forks, and 0 watches; latest commit 2026-08-31.
Conclusion: Resolved npm release 0.1.11, published 2026-08-31, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. 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 3 code capabilities: may read environment variables, 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: multi-channel-notify@0.1.11; SHA-256: e8493ca71f6286339615790c21e17eec48452678f528c9b3d1b4a2a67b4400a0.
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 multi-channel-notify. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
multi-channel-notifyAnalyzed 0.1.11github:lzylyd/multi-channel-notifyExact version not resolved