What it may solve
Manage SSH identity keys and per-host ssh config from the web settings page, so git-over-ssh works in headless server mode.
Imported third-party catalog description; not a Registry verification conclusion.Manage SSH identity keys and per-host ssh config from the web settings page, so git-over-ssh works in headless server mode.
Author: AndreasSeidl · Git & Code Review · Catalog snapshot: 2026-09-19Canonical semantic path
Manage SSH identity keys and per-host ssh config from the web settings page, so git-over-ssh works in headless server mode.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 0 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, 2 commits, 0 forks, and 0 watches; latest commit 2026-09-04.
Conclusion: Resolved npm release 0.3.0, published 2026-09-04, 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 found 6 characteristics that need attention: contains credential or token handling code, may execute dynamically constructed code, may read environment variables, may create or modify files, may access the network, may start external processes. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-ssh-manager@0.3.0; SHA-256: e0ca3f6fe9c754ae54fd91f8a7ec77bfa00949422c8ea5f12f11b10ebda6bffa.
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-ssh-manager. 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-ssh-managerAnalyzed 0.3.0github:AndreasSeidl/dsh-ssh-managerExact version not resolved