node-ssh
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:sb-scandir | AI (dependencies): Same author (steelbrain) as node-ssh; stable companion package. | ai | |
| dependencies | unvetted-dep:sb-promise-queue | AI (dependencies): Same author (steelbrain) as node-ssh; stable companion package. | ai | |
| dependencies | unvetted-dep:shell-escape | AI (dependencies): Well-known utility package; used for SSH command escaping, appropriate for this library. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 13.2.1 | 6 / 11 | |
| 13.2.0 | 6 / 11 | |
| 13.1.0 | 7 / 7 | |
| 13.0.1 | 6 / 8 | |
| 13.0.0 | 6 / 8 |
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.