theme-ui
The Design Graph Framework
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jxnblk → hasparus is a documented, legitimate maintainer transition for the theme-ui project; hasparus is a known contributor with a strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): hasparus is a recognized theme-ui maintainer; this addition reflects a legitimate project handoff, not a compromise. | ai | |
| provenance | missing-githead | AI (provenance): Established package with strong publisher track record; missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): theme-ui is a long-standing, widely trusted package; lack of Sigstore attestation is a hygiene gap, not a security risk given the publisher's history. | ai |
Versions (showing 10 of 110)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 7 / 12 | |
| 0.0.9 | 8 / 12 | |
| 0.0.8 | 7 / 12 | |
| 0.0.7 | 7 / 12 | |
| 0.0.6 | 7 / 12 | |
| 0.0.5 | 7 / 12 | |
| 0.0.4 | 7 / 11 | |
| 0.0.3 | 7 / 11 | |
| 0.0.2 | 7 / 11 | |
| 0.0.1 | 7 / 11 |
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.
v0.0.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.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.
v0.0.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.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.