@spscommerce/ds-web-components
SPS Design System Native Web Components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:incremental-dom | AI (dependencies): incremental-dom is a well-known Google library; stable dependency for this package across versions. | ai | |
| phantom-deps | phantom-dep:incremental-dom | AI (phantom-deps): incremental-dom is a legitimate build-time/config dependency; phantom-dep false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal design system library; sparse README and no keywords are expected for private org packages. | ai |
Versions (showing 100 of 241)
| Version | Deps | Published |
|---|---|---|
| 8.31.6 | 1 / 8 | |
| 8.31.5 | 1 / 8 | |
| 8.31.4 | 1 / 8 | |
| 8.31.3 | 1 / 8 | |
| 8.31.2 | 1 / 8 | |
| 8.31.1 | 1 / 8 | |
| 8.31.0 | 1 / 8 | |
| 8.30.1 | 1 / 8 | |
| 8.30.0 | 1 / 8 | |
| 8.29.10 | 1 / 8 | |
| 8.29.9 | 1 / 8 | |
| 8.29.8 | 1 / 8 | |
| 8.29.7 | 1 / 8 | |
| 8.29.6 | 1 / 8 | |
| 8.29.5 | 1 / 8 | |
| 8.29.4 | 1 / 8 | |
| 8.29.3 | 1 / 8 | |
| 8.29.2 | 1 / 8 | |
| 8.29.1 | 1 / 8 | |
| 8.29.0 | 1 / 8 | |
| 8.28.5 | 1 / 8 | |
| 8.28.4 | 1 / 8 | |
| 8.28.3 | 1 / 8 | |
| 8.28.2 | 1 / 8 | |
| 8.28.1 | 1 / 8 | |
| 8.28.0 | 1 / 8 | |
| 8.27.2 | 1 / 8 | |
| 8.27.1 | 1 / 8 | |
| 8.26.8 | 1 / 8 | |
| 8.26.7 | 1 / 8 | |
| 8.26.6 | 1 / 8 | |
| 8.26.5 | 1 / 8 | |
| 8.26.4 | 1 / 8 | |
| 8.26.3 | 1 / 8 | |
| 8.26.2 | 1 / 8 | |
| 8.26.1 | 1 / 8 | |
| 8.26.0 | 1 / 8 | |
| 8.25.0 | 1 / 8 | |
| 8.24.2 | 1 / 8 | |
| 8.24.0 | 1 / 8 | |
| 8.23.18 | 1 / 8 | |
| 8.23.17 | 1 / 8 | |
| 8.23.16 | 1 / 8 | |
| 8.23.15 | 1 / 8 | |
| 8.23.14 | 1 / 8 | |
| 8.23.13 | 1 / 8 | |
| 8.23.12 | 1 / 8 | |
| 8.23.11 | 1 / 8 | |
| 8.23.10 | 1 / 8 | |
| 8.23.9 | 1 / 8 | |
| 8.23.8 | 1 / 8 | |
| 8.23.7 | 1 / 8 | |
| 8.23.6 | 1 / 8 | |
| 8.23.5 | 1 / 8 | |
| 8.23.4 | 1 / 8 | |
| 8.23.3 | 1 / 8 | |
| 8.23.2 | 1 / 8 | |
| 8.23.1 | 1 / 8 | |
| 8.23.0 | 1 / 8 | |
| 8.22.1 | 1 / 8 | |
| 8.22.0 | 1 / 8 | |
| 8.21.5 | 1 / 8 | |
| 8.21.4 | 1 / 8 | |
| 8.21.3 | 1 / 8 | |
| 8.21.2 | 1 / 8 | |
| 8.21.1 | 1 / 8 | |
| 8.21.0 | 1 / 8 | |
| 8.20.17 | 1 / 8 | |
| 8.20.16 | 1 / 8 | |
| 8.20.15 | 1 / 8 | |
| 8.20.14 | 1 / 8 | |
| 8.20.13 | 1 / 8 | |
| 8.20.12 | 1 / 8 | |
| 8.20.11 | 1 / 8 | |
| 8.20.10 | 1 / 8 | |
| 8.20.9 | 1 / 8 | |
| 8.20.8 | 1 / 8 | |
| 8.20.7 | 1 / 8 | |
| 8.20.6 | 1 / 8 | |
| 8.20.5 | 1 / 8 | |
| 8.20.4 | 1 / 8 | |
| 8.20.3 | 1 / 8 | |
| 8.20.2 | 1 / 8 | |
| 8.20.1 | 1 / 8 | |
| 8.20.0 | 1 / 8 | |
| 8.19.12 | 1 / 8 | |
| 8.19.11 | 1 / 8 | |
| 8.19.10 | 1 / 8 | |
| 8.19.9 | 1 / 8 | |
| 8.19.8 | 1 / 8 | |
| 8.19.7 | 1 / 8 | |
| 8.19.6 | 1 / 8 | |
| 8.19.5 | 1 / 8 | |
| 8.19.4 | 1 / 8 | |
| 8.19.3 | 1 / 8 | |
| 8.19.2 | 1 / 8 | |
| 8.19.1 | 1 / 8 | |
| 8.19.0 | 1 / 8 | |
| 8.18.0 | 1 / 8 | |
| 8.17.2 | 1 / 8 |
v8.29.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.