What it may solve
Capture selected DSH, local MCP, or native WebMCP calls as reviewed, parameterized routines, expose typed tools, and replay with fresh approval.
Imported third-party catalog description; not a Registry verification conclusion.Capture selected DSH, local MCP, or native WebMCP calls as reviewed, parameterized routines, expose typed tools, and replay with fresh approval.
Author: sjh9714 · Workflow & Automation · Catalog snapshot: 2026-09-19Canonical semantic path
Capture selected DSH, local MCP, or native WebMCP calls as reviewed, parameterized routines, expose typed tools, and replay with fresh approval.
Imported third-party catalog description; not a Registry verification conclusion.1 stars · 541 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, 5 commits, 0 forks, and 0 watches; latest commit 2026-09-05.
Conclusion: Resolved npm release 0.2.0, published 2026-09-05, 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 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: routinekit@0.2.0; SHA-256: 559a43314fda939c27d286169723058d38e2c93e6c7860211adb4638bb8fa9d2.
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 routinekit. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
routinekitAnalyzed 0.2.0github:sjh9714/routinekitExact version not resolved