@salesforce/plugin-packaging
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@salesforce/packaging | AI (dependencies): @salesforce/packaging is a first-party Salesforce dependency that is the natural and expected core library for this packaging plugin; not a suspicious third-party package. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce uses its own signing infrastructure (publicKeyUrl/signatureUrl in package.json); lack of Sigstore provenance is acceptable for this publisher. | ai |
Versions (showing 7 of 111)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 6 / 8 | |
| 2.14.0 | 6 / 8 | |
| 2.13.6 | 6 / 8 | |
| 2.13.5 | 6 / 8 | |
| 2.13.4 | 6 / 8 | |
| 2.13.3 | 6 / 8 | |
| 2.13.2 | 6 / 8 |
v2.15.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.
v2.14.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.
v2.13.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.
v2.13.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.
v2.13.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.
v2.13.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.
v2.13.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.