@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 51 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.28.6 | 6 / 9 | |
| 2.28.5 | 6 / 9 | |
| 2.28.4 | 6 / 9 | |
| 2.28.3 | 6 / 9 | |
| 2.28.2 | 6 / 9 | |
| 2.28.0 | 6 / 9 | |
| 2.27.17 | 6 / 9 | |
| 2.27.16 | 6 / 9 | |
| 2.27.15 | 6 / 9 | |
| 2.27.14 | 6 / 9 | |
| 2.27.13 | 6 / 9 | |
| 2.27.12 | 6 / 9 | |
| 2.27.11 | 6 / 9 | |
| 2.27.10 | 6 / 9 | |
| 2.27.9 | 6 / 9 | |
| 2.27.8 | 6 / 9 | |
| 2.27.7 | 6 / 9 | |
| 2.27.6 | 6 / 9 | |
| 2.27.5 | 6 / 9 | |
| 2.27.4 | 6 / 9 | |
| 2.27.3 | 6 / 9 | |
| 2.27.2 | 6 / 9 | |
| 2.27.1 | 6 / 9 | |
| 2.27.0 | 6 / 9 | |
| 2.26.4 | 6 / 9 | |
| 2.26.3 | 6 / 9 | |
| 2.26.2 | 6 / 9 | |
| 2.26.1 | 6 / 9 | |
| 2.26.0 | 6 / 9 | |
| 2.25.17 | 6 / 9 | |
| 2.25.16 | 6 / 9 | |
| 2.25.15 | 6 / 9 | |
| 2.25.14 | 6 / 9 | |
| 2.25.13 | 6 / 9 | |
| 2.25.12 | 6 / 9 | |
| 2.25.11 | 6 / 9 | |
| 2.25.10 | 6 / 9 | |
| 2.25.9 | 6 / 9 | |
| 2.25.8 | 6 / 9 | |
| 2.25.7 | 6 / 9 | |
| 2.25.6 | 6 / 9 | |
| 2.25.5 | 6 / 9 | |
| 2.25.4 | 6 / 9 | |
| 2.25.3 | 6 / 9 | |
| 2.25.2 | 6 / 9 | |
| 2.25.1 | 6 / 9 | |
| 2.25.0 | 6 / 9 | |
| 2.24.11 | 6 / 9 | |
| 2.24.10 | 6 / 9 | |
| 2.24.9 | 6 / 9 | |
| 2.24.8 | 6 / 9 |
v2.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.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.
v2.25.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.
v2.25.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.