@salesforce-ux/design-system
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires exclusively in bundled MDX doc chunks; standard webpack/template pattern for this design system package. | ai | |
| provenance | no-provenance | AI (provenance): Established Salesforce org package; lack of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.30.4 | 0 / 0 | |
| 2.30.3 | 0 / 0 | |
| 2.30.2 | 0 / 0 | |
| 2.30.1 | 0 / 0 | |
| 2.30.0 | 0 / 0 | |
| 2.29.2 | 0 / 0 |
v2.30.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: salesforce-ux.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.