@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 100 of 207)
| Version | Deps | Published |
|---|---|---|
| 5.9.21 | 12 / 10 | |
| 5.9.20 | 12 / 10 | |
| 5.9.19 | 12 / 10 | |
| 5.9.18 | 12 / 10 | |
| 5.9.17 | 12 / 10 | |
| 5.9.16 | 12 / 10 | |
| 5.9.15 | 12 / 10 | |
| 5.9.14 | 12 / 10 | |
| 5.9.13 | 12 / 10 | |
| 5.9.12 | 12 / 10 | |
| 5.9.11 | 12 / 10 | |
| 5.9.10 | 12 / 10 | |
| 5.9.9 | 12 / 10 | |
| 5.9.8 | 12 / 10 | |
| 5.9.7 | 12 / 10 | |
| 5.9.6 | 12 / 10 | |
| 5.9.5 | 12 / 10 | |
| 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 | |
| 5.7.0 | 12 / 10 | |
| 5.6.3 | 12 / 10 | |
| 5.6.2 | 12 / 10 | |
| 5.6.1 | 12 / 10 | |
| 5.6.0 | 12 / 10 | |
| 5.5.8 | 12 / 10 | |
| 5.5.7 | 12 / 10 | |
| 5.5.6 | 12 / 10 | |
| 5.5.5 | 12 / 10 | |
| 5.5.4 | 12 / 10 | |
| 5.5.3 | 12 / 10 | |
| 5.5.2 | 12 / 10 | |
| 5.5.1 | 12 / 10 | |
| 5.5.0 | 12 / 10 | |
| 5.4.1 | 12 / 10 | |
| 5.4.0 | 12 / 10 | |
| 5.3.0 | 12 / 10 | |
| 5.2.42 | 12 / 10 | |
| 5.2.41 | 12 / 10 | |
| 5.2.40 | 12 / 10 | |
| 5.2.39 | 12 / 10 | |
| 5.2.38 | 12 / 10 | |
| 5.2.37 | 12 / 10 | |
| 5.2.36 | 12 / 10 | |
| 5.2.35 | 12 / 10 | |
| 5.2.34 | 12 / 10 | |
| 5.2.33 | 12 / 10 | |
| 5.2.32 | 12 / 10 | |
| 5.2.31 | 12 / 10 | |
| 5.2.30 | 12 / 10 | |
| 5.2.29 | 12 / 10 | |
| 5.2.28 | 12 / 10 | |
| 5.2.27 | 12 / 10 | |
| 5.2.26 | 12 / 10 | |
| 5.2.25 | 12 / 10 | |
| 5.2.24 | 12 / 10 | |
| 5.2.23 | 12 / 10 | |
| 5.2.18 | 12 / 10 | |
| 5.2.17 | 12 / 10 | |
| 5.2.16 | 12 / 10 | |
| 5.2.15 | 12 / 10 | |
| 5.2.14 | 12 / 10 | |
| 5.2.13 | 12 / 10 | |
| 5.2.12 | 12 / 10 | |
| 5.2.11 | 12 / 10 | |
| 5.2.10 | 12 / 10 | |
| 5.2.9 | 12 / 10 | |
| 5.2.8 | 12 / 10 | |
| 5.2.7 | 12 / 10 | |
| 5.2.6 | 12 / 10 | |
| 5.2.5 | 12 / 10 | |
| 5.2.4 | 12 / 10 | |
| 5.2.3 | 12 / 10 | |
| 5.2.2 | 12 / 10 | |
| 5.2.1 | 12 / 10 | |
| 5.2.0 | 12 / 10 | |
| 5.1.5 | 12 / 10 | |
| 5.1.4 | 11 / 10 |
v5.7.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.6.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.6.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.6.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.6.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.5.8
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.5.7
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.5.6
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.5.5
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.5.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.5.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.5.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.5.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.5.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.4.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.4.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.3.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.2.42
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.2.41
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.2.40
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.2.39
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.2.38
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.2.37
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.2.36
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.2.35
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.2.34
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.2.33
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.2.32
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.2.31
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.2.30
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.2.29
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.2.28
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.2.27
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.2.26
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.2.25
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.2.24
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.2.23
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.2.18
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.2.17
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.2.16
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.2.15
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.2.14
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.2.13
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.2.12
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.2.11
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.2.10
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.2.9
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.2.8
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.2.7
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.2.6
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.2.5
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.2.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.2.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.2.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.2.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.2.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.1.5
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.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.