ssh2-streams
SSH2 and SFTP(v3) client/server protocol streams for node.js
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:mscdex-ssh2-streams-60ab5e9/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js fs API compatibility shim; the sample shows only utility/error-formatting helpers, not actual network calls or malicious dynamic execution. False positive for this SSH protocol library. | ai | |
| source-diff | net-exec-file:mscdex-ssh2-streams-d81fde1/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js compatibility shim with no actual network calls or malicious execution. SSH2 is a network protocol library; the analyzer conflates protocol-level network use with dropper behavior. False positive for this package. | ai | |
| source-diff | net-exec-file:mscdex-ssh2-streams-635dfaa/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js compatibility shim polyfilling internal error classes and utilities for older Node versions. No actual network calls or malicious code execution present. | ai | |
| provenance | no-provenance | AI (provenance): Established package by trusted maintainer mscdex; lack of Sigstore provenance is a hygiene note, not a security risk for this package. | ai | |
| source-diff | net-exec-file:mscdex-ssh2-streams-0693339/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js compatibility shim with no actual network calls; the dynamic code execution is a BigInt polyfill pattern in a crypto library. False positive for this package. | ai | |
| source-diff | net-exec-file:mscdex-ssh2-streams-dfff10b/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js internal API compatibility shim with no actual network calls or malicious dynamic execution; false positive for this SSH protocol library. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require uses __dirname + relative path for sibling module loading — not user-controlled input. Standard pattern in this codebase. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is core functionality for an SSH key parser — SSH keys are base64-encoded by specification. Not a malicious payload indicator. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in keyParser.js generates optimized crypto code paths based on runtime BigInt availability. Inputs are controlled internal strings, not user data. Legitimate pattern in crypto libraries. | ai | |
| source-diff | net-exec-file:mscdex-ssh2-streams-5e03147/lib/node-fs-compat.js | AI (source-diff): node-fs-compat.js is a Node.js fs compatibility shim with error classes and polyfills. No actual network calls or malicious code execution present; false positive for this SSH library. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard in SSH/crypto key parsing. Expected and legitimate for this package's purpose. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.4.10 | 3 / 0 | |
| 0.4.9 | 3 / 0 | |
| 0.4.8 | 3 / 0 | |
| 0.4.7 | 3 / 0 | |
| 0.4.6 | 3 / 0 | |
| 0.4.5 | 3 / 0 | |
| 0.4.4 | 3 / 0 | |
| 0.4.3 | 3 / 0 | |
| 0.4.2 | 3 / 0 | |
| 0.4.1 | 3 / 0 | |
| 0.4.0 | 3 / 0 | |
| 0.3.3 | 3 / 0 | |
| 0.3.2 | 3 / 0 | |
| 0.3.1 | 3 / 0 | |
| 0.3.0 | 3 / 0 | |
| 0.2.1 | 3 / 0 | |
| 0.2.0 | 3 / 0 | |
| 0.1.20 | 3 / 0 | |
| 0.1.19 | 3 / 0 | |
| 0.1.18 | 3 / 0 | |
| 0.1.16 | 3 / 0 | |
| 0.1.15 | 3 / 0 | |
| 0.1.14 | 3 / 0 | |
| 0.1.13 | 3 / 0 | |
| 0.1.12 | 3 / 0 | |
| 0.1.11 | 3 / 0 | |
| 0.1.10 | 3 / 0 | |
| 0.1.9 | 3 / 0 | |
| 0.1.8 | 3 / 0 | |
| 0.1.7 | 3 / 0 | |
| 0.1.6 | 3 / 0 | |
| 0.1.5 | 3 / 0 | |
| 0.1.4 | 3 / 0 | |
| 0.1.3 | 3 / 0 | |
| 0.1.2 | 3 / 0 | |
| 0.1.1 | 3 / 0 | |
| 0.1.0 | 3 / 0 | |
| 0.0.23 | 3 / 0 | |
| 0.0.22 | 3 / 0 | |
| 0.0.21 | 3 / 0 | |
| 0.0.20 | 3 / 0 | |
| 0.0.19 | 3 / 0 | |
| 0.0.18 | 4 / 0 | |
| 0.0.17 | 4 / 0 | |
| 0.0.16 | 4 / 0 | |
| 0.0.15 | 4 / 0 | |
| 0.0.14 | 4 / 0 | |
| 0.0.13 | 4 / 0 | |
| 0.0.12 | 4 / 0 | |
| 0.0.11 | 4 / 0 | |
| 0.0.10 | 4 / 0 |
v0.4.10
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.