@theme-ui/components — Greenflagged

Primitive layout, typographic, and other components for use with Theme UI.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jxnblkjohnohasparuslachlanjc

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): @theme-ui/core is a same-namespace monorepo dependency at the same version; this is an internal refactor, not a third-party supply chain risk.	ai	2026/04/24
phantom-deps	phantom-dep:@styled-system/color	AI (phantom-deps): Declared as a dependency and used via build config/transitive usage in this monorepo package; stable false positive for @theme-ui/components.	ai	2026/04/24
phantom-deps	phantom-dep:@types/styled-system	AI (phantom-deps): Type-only dependency loaded by convention in TypeScript monorepo; stable false positive for @theme-ui/components.	ai	2026/04/24
phantom-deps	phantom-dep:@styled-system/should-forward-prop	AI (phantom-deps): Declared as a dependency and used via build config/transitive usage in this monorepo package; stable false positive for @theme-ui/components.	ai	2026/04/24
phantom-deps	phantom-dep:@styled-system/space	AI (phantom-deps): Declared as a dependency and used via build config/transitive usage in this monorepo package; stable false positive for @theme-ui/components.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): hasparus is a known Theme UI contributor with a strong track record. The maintainer addition reflects a legitimate project handoff, not a compromise.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): hasparus is a long-standing, trusted npm publisher (540 approved packages, 0 rejected) who took over Theme UI maintenance from jxnblk. This transition is legitimate and stable for this package.	ai	2026/04/24

Versions (showing 53 of 53)

Version	Deps	Published
0.17.4	6 / 4	2026-01-02
0.17.2	6 / 4	2025-02-14
0.17.1	6 / 4	2024-10-24
0.17.0	6 / 4	2024-10-18
0.16.2	6 / 4	2024-02-19
0.16.1	6 / 4	2023-08-14
0.16.0	6 / 4	2023-06-15
0.15.5	5 / 6	2023-02-07
0.15.4	5 / 6	2022-11-10
0.15.1	5 / 6	2022-09-26
0.14.7	5 / 1	2022-07-28
0.14.6	5 / 1	2022-06-15
0.14.5	5 / 1	2022-04-30
0.14.4	5 / 1	2022-04-23
0.14.3	5 / 1	2022-04-21
0.14.2	5 / 1	2022-03-31
0.14.1	5 / 1	2022-03-22
0.14.0	5 / 1	2022-03-21
0.13.1	5 / 1	2022-01-05
0.13.0	5 / 1	2021-12-27
0.12.1	7 / 1	2021-11-22
0.12.0	7 / 1	2021-10-28
0.11.3	7 / 1	2021-09-24
0.11.2	7 / 1	2021-09-08
0.11.1	7 / 1	2021-08-25
0.11.0	7 / 1	2021-08-25
0.10.0	7 / 1	2021-06-19
0.9.1	7 / 1	2021-05-26
0.9.0	7 / 1	2021-05-25
0.8.4	7 / 1	2021-05-06
0.8.3	7 / 1	2021-05-05
0.8.2	7 / 1	2021-05-05
0.8.1	7 / 1	2021-05-05
0.8.0	7 / 1	2021-05-05
0.7.5	7 / 1	2021-04-28
0.7.4	7 / 1	2021-04-27
0.7.3	7 / 1	2021-04-21
0.7.2	7 / 1	2021-04-19
0.7.1	7 / 1	2021-04-19
0.7.0	7 / 1	2021-04-15
0.6.2	7 / 1	2021-04-05
0.6.1	7 / 1	2021-03-30
0.6.0	7 / 1	2021-03-22
0.4.0	6 / 0	2020-10-16
0.3.5	6 / 0	2020-12-21
0.3.4	6 / 0	2020-11-20
0.3.3	6 / 0	2020-11-08
0.3.2	6 / 0	2020-11-08
0.3.1	6 / 0	2020-01-23
0.3.0	6 / 0	2020-01-22
0.2.50	6 / 0	2019-12-02
0.2.49	6 / 0	2019-11-15
0.2.46	5 / 0	2019-10-28

v0.17.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hasparus.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hasparus.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hasparus.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hasparus.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hasparus.

HIGH Publisher changed: jxnblk → hasparus (on 2020-10-16) provenance

This version was published by a different npm account than previous versions on 2020-10-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

2 findings

HIGH Publisher changed: jxnblk → hasparus (on 2020-11-20) provenance

This version was published by a different npm account than previous versions on 2020-11-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

2 findings

HIGH Publisher changed: jxnblk → hasparus (on 2020-11-08) provenance

This version was published by a different npm account than previous versions on 2020-11-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

2 findings

HIGH Publisher changed: jxnblk → hasparus (on 2020-11-08) provenance

This version was published by a different npm account than previous versions on 2020-11-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.46

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.