@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, so a manually published version cannot be tied back to a reviewed commit.
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 7 of 207)
| Version | Deps | Published |
|---|---|---|
| 5.1.3 | 11 / 10 | |
| 5.1.2 | 11 / 10 | |
| 5.1.1 | 11 / 10 | |
| 5.1.0 | 11 / 10 | |
| 5.0.2 | 11 / 10 | |
| 5.0.1 | 11 / 10 | |
| 5.0.0 | 11 / 10 |
v5.1.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.1.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.1.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.
v5.1.0
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.0.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.0.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.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.