@mazhu/sshmgr
SSH connection manager CLI - manage multiple SSH connections with one-click connect
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:ssh-key-access | AI (semgrep): SSH manager CLI legitimately reads user-supplied key paths; accessing ~/.ssh/id_rsa is core functionality, not credential theft. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is part of a local XOR encryption/decryption routine for stored credentials, not payload obfuscation. | ai |
v1.0.1
2 findingsAccessing SSH keys — strong indicator of credential theft 49 | { type: 'input', name: 'passphrase', message: 'Passphrase (empty if none):', default: '' } 50 | ]); > 51 | privateKey = keyAns.privateKey || '~/.ssh/id_rsa'; 52 | passphrase = keyAns.passphrase || ''; 53 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsAccessing SSH keys — strong indicator of credential theft 49 | { type: 'input', name: 'passphrase', message: 'Passphrase (empty if none):', default: '' } 50 | ]); > 51 | privateKey = keyAns.privateKey || '~/.ssh/id_rsa'; 52 | passphrase = keyAns.passphrase || ''; 53 | }
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.