@things-factory/integration-sftp
Integration With SFTP
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ftp | AI (phantom-deps): ftp is a legitimate runtime dep for an SFTP integration package; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:ssh2 | AI (phantom-deps): ssh2 is a legitimate runtime dep used by ssh2-sftp-client; phantom detection is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 7 / 0 | |
| 9.2.23 | 7 / 0 | |
| 9.2.22 | 7 / 0 | |
| 9.2.21 | 7 / 0 | |
| 9.2.20 | 7 / 0 | |
| 9.2.13 | 7 / 0 | |
| 8.0.87 | 7 / 0 | |
| 4.3.791 | 10 / 0 | |
| 4.3.755 | 10 / 0 | |
| 4.3.701 | 10 / 0 | |
| 4.3.637 | 7 / 0 |
v9.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.791
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.755
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.701
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.637
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.