jsftp
A sane FTP client implementation for NodeJS
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:ftpd | AI (npm-metadata): Dev-only test dependency pinned to a commit; not part of runtime/install path. | ai | |
| provenance | no-provenance | AI (provenance): jsftp is a long-established package (14+ years, 84 versions) published well before Sigstore provenance was common practice. Absence of attestation is expected and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 6 / 5 | |
| 2.1.2 | 6 / 9 | |
| 2.1.1 | 6 / 9 | |
| 2.1.0 | 6 / 9 | |
| 2.0.0 | 6 / 8 |
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.