@salesforce/cli
The Salesforce CLI
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Salesforce CLI's preinstall script runs a local JS file for pre-installation checks; standard for this CLI framework. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: @salesforce/cli is the official Salesforce CLI, not a typosquat of 'joi'. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.137.1 | 34 / 10 | |
| 2.137.0 | 34 / 10 | |
| 2.136.6 | 34 / 10 | |
| 2.136.4 | 34 / 10 | |
| 2.134.5 | 34 / 10 | |
| 2.134.4 | 34 / 10 | |
| 2.134.3 | 34 / 10 | |
| 2.134.2 | 34 / 10 | |
| 2.134.1 | 34 / 10 | |
| 2.133.4 | 34 / 10 | |
| 2.131.7 | 34 / 10 | |
| 2.130.7 | 34 / 10 | |
| 2.130.6 | 34 / 10 | |
| 2.130.1 | 34 / 10 | |
| 2.130.0 | 34 / 10 | |
| 2.111.4 | 34 / 10 | |
| 2.87.3 | 33 / 9 | |
| 2.87.2 | 33 / 9 | |
| 2.87.1 | 33 / 9 |
v2.137.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.134.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.133.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.131.7
2 findingsScript: node ./scripts/preinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.130.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.130.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.130.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.130.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.