What it may solve
Config-driven lifecycle hooks: event→command declarations in cordis.patch.yml, with Feishu card notifications and a QR scan-to-create bot setup.
Imported third-party catalog description; not a Registry verification conclusion.dsh-hooks
Automated evidence availableConfig-driven lifecycle hooks: event→command declarations in cordis.patch.yml, with Feishu card notifications and a QR scan-to-create bot setup.
Author: PeterBon · Notifications & Integrations · Catalog snapshot: 2026-09-19Canonical semantic path
Workflow & AutomationEvent & Condition Triggers
One primary path; alternate capabilities remain separate.Sources and public signals
6 stars · 1865 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19What can currently be confirmed
Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure
Source structure has not been analyzed.
Repository health
Repository metadata has not been analyzed.
npm release
npm release metadata has not been analyzed.
DSH compatibility
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Dependency audit
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
Functional verification
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Static risk scan
Conclusion: The scan found 7 characteristics that need attention: contains credential or token handling code, may read environment variables, may create or modify files, may access the network, may start external processes, may execute shell commands, test, example, or support code contains additional capabilities outside the default runtime scope. This is a bounded automated observation, not a determination of malicious intent.
Package integrity
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-hooks@0.13.1; SHA-256: 4e73ec54ec3cd7eaf024ec07065dd303a247da40919983e76c433e2cad3410c1.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Continue with the latest plugin manager
Describe your task in a DSH conversation and mention dsh-hooks. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
Sources available for local inspection
- npm package
dsh-hooksAnalyzed 0.13.1 - GitHub source
github:PeterBon/dsh-hooksExact version not resolved