@spinajs/fs-ftp
file operations implementation for ftp
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:basic-ftp | AI (phantom-deps): Core FTP dep for this package; imported in compiled lib, not raw TS sources scanned. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Utility dep consistent with spinajs ecosystem; stable false positive. | ai | |
| phantom-deps | phantom-dep:luxon | AI (phantom-deps): Date utility dep consistent with spinajs ecosystem; stable false positive. | ai | |
| phantom-deps | phantom-dep:@spinajs/di | AI (phantom-deps): Same-org dep; expected in spinajs monorepo packages. | ai | |
| phantom-deps | phantom-dep:@spinajs/fs | AI (phantom-deps): Same-org dep; expected in spinajs monorepo packages. | ai | |
| phantom-deps | phantom-dep:@spinajs/log | AI (phantom-deps): Same-org dep; expected in spinajs monorepo packages. | ai | |
| phantom-deps | phantom-dep:@spinajs/configuration | AI (phantom-deps): Same-org dep; expected in spinajs monorepo packages. | ai |
Versions (showing 5 of 111)
| Version | Deps | Published |
|---|---|---|
| 2.0.367 | 7 / 1 | |
| 2.0.363 | 7 / 1 | |
| 2.0.362 | 7 / 1 | |
| 2.0.361 | 7 / 1 | |
| 2.0.360 | 7 / 1 |
v2.0.367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.