@spark-web/design-system
--- title: 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, 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo aggregator; sparse metadata is expected for this package type. | ai | |
| phantom-deps | phantom-dep:@spark-web/ssr | AI (phantom-deps): Same-org re-export package; phantom-dep is a false positive for aggregator packages. | ai | |
| phantom-deps | phantom-dep:@spark-web/next-utils | AI (phantom-deps): Same-org re-export package; phantom-dep is a false positive for aggregator packages. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 5.1.11 | 57 / 0 | |
| 5.1.10 | 57 / 0 | |
| 5.1.9 | 57 / 0 | |
| 5.1.8 | 57 / 0 | |
| 5.1.7 | 57 / 0 | |
| 5.1.6 | 57 / 0 | |
| 5.1.5 | 57 / 0 | |
| 5.1.4 | 57 / 0 | |
| 5.1.3 | 57 / 0 | |
| 5.1.1 | 57 / 0 | |
| 5.0.96 | 49 / 0 | |
| 5.0.82 | 47 / 0 | |
| 5.0.70 | 47 / 0 | |
| 5.0.68 | 47 / 0 | |
| 5.0.64 | 47 / 0 | |
| 5.0.53 | 47 / 0 | |
| 5.0.52 | 47 / 0 | |
| 5.0.50 | 47 / 0 | |
| 5.0.49 | 47 / 0 | |
| 5.0.48 | 47 / 0 | |
| 5.0.47 | 47 / 0 | |
| 5.0.46 | 47 / 0 | |
| 5.0.45 | 47 / 0 | |
| 5.0.44 | 47 / 0 | |
| 5.0.43 | 47 / 0 | |
| 5.0.42 | 47 / 0 | |
| 5.0.41 | 47 / 0 | |
| 5.0.40 | 47 / 0 | |
| 5.0.39 | 47 / 0 | |
| 5.0.38 | 47 / 0 | |
| 5.0.37 | 47 / 0 | |
| 5.0.36 | 47 / 0 | |
| 5.0.35 | 47 / 0 | |
| 5.0.34 | 47 / 0 | |
| 5.0.33 | 47 / 0 | |
| 5.0.32 | 47 / 0 | |
| 5.0.31 | 47 / 0 | |
| 5.0.30 | 47 / 0 | |
| 5.0.29 | 47 / 0 | |
| 5.0.28 | 47 / 0 | |
| 5.0.27 | 47 / 0 | |
| 5.0.26 | 47 / 0 | |
| 5.0.25 | 47 / 0 | |
| 5.0.24 | 47 / 0 | |
| 5.0.23 | 47 / 0 | |
| 5.0.22 | 47 / 0 | |
| 5.0.21 | 47 / 0 | |
| 5.0.19 | 47 / 0 | |
| 5.0.18 | 47 / 0 | |
| 5.0.16 | 47 / 0 | |
| 5.0.15 | 47 / 0 | |
| 5.0.14 | 47 / 0 | |
| 5.0.13 | 47 / 0 | |
| 5.0.12 | 47 / 0 | |
| 5.0.11 | 47 / 0 | |
| 5.0.10 | 47 / 0 | |
| 5.0.9 | 47 / 0 | |
| 5.0.8 | 47 / 0 | |
| 5.0.7 | 47 / 0 | |
| 5.0.6 | 47 / 0 | |
| 5.0.5 | 47 / 0 | |
| 5.0.4 | 47 / 0 | |
| 5.0.3 | 47 / 0 | |
| 5.0.2 | 47 / 0 | |
| 5.0.1 | 47 / 0 | |
| 5.0.0 | 47 / 0 |
v5.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.