@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, 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 |
|---|---|---|---|---|
| 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 46 of 248)
| Version | Deps | Published |
|---|---|---|
| 2.0.266 | 7 / 1 | |
| 2.0.265 | 7 / 1 | |
| 2.0.264 | 7 / 1 | |
| 2.0.263 | 7 / 1 | |
| 2.0.262 | 7 / 1 | |
| 2.0.261 | 7 / 1 | |
| 2.0.260 | 7 / 1 | |
| 2.0.259 | 7 / 1 | |
| 2.0.258 | 7 / 1 | |
| 2.0.257 | 7 / 1 | |
| 2.0.256 | 7 / 1 | |
| 2.0.255 | 7 / 1 | |
| 2.0.254 | 7 / 1 | |
| 2.0.253 | 7 / 1 | |
| 2.0.252 | 7 / 1 | |
| 2.0.251 | 7 / 1 | |
| 2.0.250 | 7 / 1 | |
| 2.0.249 | 7 / 1 | |
| 2.0.248 | 7 / 1 | |
| 2.0.247 | 7 / 1 | |
| 2.0.246 | 7 / 1 | |
| 2.0.245 | 7 / 1 | |
| 2.0.244 | 7 / 1 | |
| 2.0.243 | 7 / 1 | |
| 2.0.242 | 7 / 1 | |
| 2.0.241 | 7 / 1 | |
| 2.0.240 | 7 / 1 | |
| 2.0.238 | 7 / 1 | |
| 2.0.237 | 7 / 1 | |
| 2.0.236 | 7 / 1 | |
| 2.0.235 | 7 / 1 | |
| 2.0.234 | 7 / 1 | |
| 2.0.233 | 7 / 1 | |
| 2.0.232 | 7 / 1 | |
| 2.0.231 | 7 / 1 | |
| 2.0.230 | 7 / 1 | |
| 2.0.229 | 7 / 1 | |
| 2.0.228 | 7 / 1 | |
| 2.0.227 | 7 / 1 | |
| 2.0.226 | 7 / 1 | |
| 2.0.225 | 7 / 1 | |
| 2.0.224 | 7 / 1 | |
| 2.0.223 | 7 / 1 | |
| 2.0.222 | 7 / 1 | |
| 2.0.221 | 7 / 1 | |
| 2.0.220 | 7 / 1 |
v2.0.266
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.265
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.264
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.263
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.262
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.261
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.260
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.259
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.256
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.255
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.254
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.253
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.250
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.249
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.248
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.247
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.220
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.