What it may solve
Ship a project to Cloudflare and publish your plugin to npm — the first deploy needs no cloud account, and credentials never reach the model.
Imported third-party catalog description; not a Registry verification conclusion.dsh-plugin-deploy
Automated evidence availableShip a project to Cloudflare and publish your plugin to npm — the first deploy needs no cloud account, and credentials never reach the model.
Author: Octo-o-o-o · Development & Runtime · Catalog snapshot: 2026-09-19Canonical semantic path
Infrastructure & System IntegrationRemote Deployment & Cloud Operations
One primary path; alternate capabilities remain separate.Sources and public signals
2 stars · 459 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 5/5. Historical chains are retained but do not count toward current coverage.
Source structure
Conclusion: The source structure check completed without finding a structural issue.
Repository health
Conclusion: The GitHub repository is reachable and not archived. Public data: 2 stars, 12 commits, 0 forks, and 0 watches; latest commit 2026-09-04.
npm release
Conclusion: Resolved npm release 0.1.3, published 2026-08-21, license MIT.
DSH compatibility
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.
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 observed 2 code capabilities: may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Package integrity
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-plugin-deploy@0.1.3; SHA-256: 948b7461d6dff566d5eb6f86566e92043a6d2eeb0a5845544d089fd7efda1630.
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-plugin-deploy. 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-plugin-deployAnalyzed 0.1.3 - GitHub source
github:Octo-o-o-o/dsh-plugin-deployExact version not resolved