@edirect/sftp-client
SFTP client module for eDirect NestJS applications. Provides a `SftpClientService` with methods for uploading, downloading, listing, renaming, and deleting files on SFTP servers — backed by `ssh2-sftp-client`.
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
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 11.0.58 | 3 / 2 | |
| 11.0.56 | 3 / 2 | |
| 11.0.55 | 3 / 2 | |
| 11.0.54 | 3 / 2 | |
| 11.0.53 | 3 / 2 | |
| 11.0.44 | 3 / 2 | |
| 11.0.42 | 3 / 2 | |
| 11.0.38 | 3 / 2 | |
| 11.0.34 | 3 / 2 | |
| 11.0.32 | 3 / 2 | |
| 11.0.31 | 3 / 2 | |
| 11.0.29 | 3 / 2 |
v11.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.