@salesforce/plugin-apex
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:color-name | AI (phantom-deps): Small color util dep likely used via color-convert indirection; benign for this official Salesforce plugin. | ai | |
| dependencies | unvetted-dep:@salesforce/apex-node | AI (dependencies): @salesforce/apex-node is a first-party Salesforce package, a natural dependency for this Apex CLI plugin; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce uses their own signing infrastructure (publicKeyUrl/signatureUrl in package.json); Sigstore provenance absence is expected and stable for this publisher. | ai |
Versions (showing 100 of 154)
| Version | Deps | Published |
|---|---|---|
| 3.9.40 | 5 / 9 | |
| 3.9.39 | 5 / 9 | |
| 3.9.38 | 5 / 9 | |
| 3.9.37 | 5 / 9 | |
| 3.9.36 | 5 / 9 | |
| 3.9.35 | 5 / 9 | |
| 3.9.34 | 5 / 9 | |
| 3.9.33 | 5 / 9 | |
| 3.9.32 | 5 / 9 | |
| 3.9.31 | 5 / 9 | |
| 3.9.30 | 5 / 9 | |
| 3.9.29 | 5 / 9 | |
| 3.9.28 | 5 / 9 | |
| 3.9.27 | 5 / 9 | |
| 3.9.26 | 5 / 9 | |
| 3.9.25 | 5 / 9 | |
| 3.9.24 | 5 / 9 | |
| 3.9.23 | 5 / 9 | |
| 3.9.22 | 5 / 9 | |
| 3.9.21 | 5 / 9 | |
| 3.9.20 | 5 / 9 | |
| 3.9.19 | 5 / 9 | |
| 3.9.18 | 5 / 9 | |
| 3.9.17 | 5 / 9 | |
| 3.9.16 | 5 / 9 | |
| 3.9.15 | 5 / 9 | |
| 3.9.14 | 5 / 9 | |
| 3.9.13 | 5 / 9 | |
| 3.9.12 | 5 / 9 | |
| 3.9.11 | 5 / 9 | |
| 3.9.10 | 5 / 9 | |
| 3.9.9 | 5 / 9 | |
| 3.9.8 | 5 / 9 | |
| 3.9.7 | 5 / 9 | |
| 3.9.6 | 5 / 9 | |
| 3.9.5 | 5 / 9 | |
| 3.9.4 | 5 / 9 | |
| 3.9.3 | 5 / 9 | |
| 3.9.2 | 5 / 9 | |
| 3.9.1 | 5 / 9 | |
| 3.9.0 | 5 / 9 | |
| 3.8.10 | 5 / 9 | |
| 3.8.9 | 5 / 9 | |
| 3.8.8 | 5 / 9 | |
| 3.8.7 | 5 / 9 | |
| 3.8.6 | 5 / 9 | |
| 3.8.5 | 5 / 9 | |
| 3.8.4 | 5 / 9 | |
| 3.8.3 | 5 / 9 | |
| 3.8.2 | 5 / 9 | |
| 3.8.1 | 5 / 9 | |
| 3.8.0 | 5 / 9 | |
| 3.7.1 | 5 / 9 | |
| 3.7.0 | 5 / 9 | |
| 3.6.19 | 5 / 9 | |
| 3.6.18 | 5 / 9 | |
| 3.6.17 | 5 / 9 | |
| 3.6.16 | 5 / 9 | |
| 3.6.15 | 5 / 9 | |
| 3.6.14 | 5 / 9 | |
| 3.6.13 | 5 / 9 | |
| 3.6.12 | 5 / 9 | |
| 3.6.11 | 5 / 9 | |
| 3.6.10 | 5 / 9 | |
| 3.6.9 | 5 / 9 | |
| 3.6.8 | 5 / 9 | |
| 3.6.7 | 5 / 9 | |
| 3.6.6 | 5 / 9 | |
| 3.6.5 | 5 / 9 | |
| 3.6.4 | 5 / 9 | |
| 3.6.3 | 5 / 9 | |
| 3.6.2 | 5 / 9 | |
| 3.6.1 | 5 / 9 | |
| 3.6.0 | 5 / 9 | |
| 3.5.6 | 5 / 9 | |
| 3.5.5 | 5 / 9 | |
| 3.5.4 | 5 / 9 | |
| 3.5.3 | 5 / 9 | |
| 3.5.2 | 5 / 9 | |
| 3.5.1 | 5 / 9 | |
| 3.5.0 | 5 / 9 | |
| 3.4.10 | 5 / 9 | |
| 3.4.9 | 5 / 9 | |
| 3.4.8 | 5 / 9 | |
| 3.4.7 | 5 / 9 | |
| 3.4.6 | 5 / 9 | |
| 3.4.5 | 5 / 9 | |
| 3.4.4 | 5 / 9 | |
| 3.4.3 | 5 / 9 | |
| 3.4.2 | 5 / 9 | |
| 3.4.1 | 5 / 9 | |
| 3.4.0 | 5 / 9 | |
| 3.3.4 | 5 / 9 | |
| 3.3.3 | 5 / 9 | |
| 3.3.2 | 5 / 9 | |
| 3.3.1 | 5 / 9 | |
| 3.3.0 | 5 / 9 | |
| 3.2.5 | 5 / 9 | |
| 3.2.4 | 5 / 9 | |
| 3.2.3 | 5 / 9 |
v3.9.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.6.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.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.
v3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.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.
v3.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.
v3.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.
v3.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.