@salesforce/source-deploy-retrieve
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:fast-levenshtein | AI (dependencies): fast-levenshtein is a well-known string distance library; its use for metadata type suggestion is legitimate and stable for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is expected behavior for this Salesforce metadata API client — the API returns ZIP files as base64 strings that must be decoded. Not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:@salesforce/types | AI (phantom-deps): First-party Salesforce package in the same org scope; phantom-dep finding is a packaging nuance, not a security risk. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 12.36.2 | 14 / 17 | |
| 12.36.1 | 14 / 17 | |
| 12.36.0 | 14 / 17 | |
| 12.35.5 | 14 / 17 | |
| 12.35.4 | 14 / 17 | |
| 12.35.3 | 14 / 17 | |
| 12.35.2 | 14 / 17 | |
| 12.35.0 | 14 / 17 | |
| 12.34.5 | 14 / 17 | |
| 12.34.4 | 14 / 17 | |
| 12.34.3 | 14 / 17 | |
| 12.34.2 | 14 / 17 | |
| 12.34.0 | 14 / 17 | |
| 12.32.9 | 14 / 17 | |
| 12.32.8 | 14 / 17 | |
| 12.32.7 | 14 / 17 | |
| 12.32.6 | 14 / 17 | |
| 12.32.5 | 14 / 17 | |
| 12.32.4 | 14 / 17 | |
| 12.32.1 | 14 / 17 | |
| 12.31.30 | 14 / 17 | |
| 12.31.29 | 14 / 17 | |
| 12.31.28 | 14 / 17 | |
| 12.31.27 | 14 / 17 | |
| 12.29.1 | 14 / 17 | |
| 12.27.2 | 14 / 17 | |
| 12.27.0 | 14 / 17 | |
| 12.26.1 | 14 / 17 | |
| 12.26.0 | 14 / 17 | |
| 12.19.4 | 15 / 17 |
v12.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.35.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.31.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.31.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.31.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.31.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.