@salesforce/plugin-org
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:is-wsl | AI (phantom-deps): is-wsl is a legitimate runtime dependency declared in package.json; used for WSL detection in platform-specific behavior. Phantom-dep finding is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce-releases is a well-established, trusted publisher with 1100+ approved packages. Package uses Salesforce's own code-signing mechanism (sfdx publicKeyUrl/signatureUrl) as an alternative integrity mechanism. | ai |
Versions (showing 25 of 126)
| Version | Deps | Published |
|---|---|---|
| 5.9.4 | 12 / 10 | |
| 5.9.3 | 12 / 10 | |
| 5.9.2 | 12 / 10 | |
| 5.9.1 | 12 / 10 | |
| 5.9.0 | 12 / 10 | |
| 5.8.5 | 12 / 10 | |
| 5.8.4 | 12 / 10 | |
| 5.8.3 | 12 / 10 | |
| 5.8.2 | 12 / 10 | |
| 5.8.1 | 12 / 10 | |
| 5.8.0 | 12 / 10 | |
| 5.7.14 | 12 / 10 | |
| 5.7.13 | 12 / 10 | |
| 5.7.12 | 12 / 10 | |
| 5.7.11 | 12 / 10 | |
| 5.7.10 | 12 / 10 | |
| 5.7.9 | 12 / 10 | |
| 5.7.8 | 12 / 10 | |
| 5.7.7 | 12 / 10 | |
| 5.7.6 | 12 / 10 | |
| 5.7.5 | 12 / 10 | |
| 5.7.4 | 12 / 10 | |
| 5.7.3 | 12 / 10 | |
| 5.7.2 | 12 / 10 | |
| 5.7.1 | 12 / 10 |
v5.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.