@theme-ui/mdx
[MDX](https://mdxjs.com) utilities for [Theme UI](https://theme-ui.com)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): @theme-ui/mdx is a scoped package in the official Theme UI monorepo; the Levenshtein match to 'mobx' is a false positive with no semantic relationship. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from jxnblk to hasparus is a documented, legitimate maintainer transition for the Theme UI monorepo. hasparus has a strong track record (529 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): hasparus is a long-standing, trusted npm account added as part of the known Theme UI maintainer transition. No compromise indicators present. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.17.4 | 2 / 8 | |
| 0.17.2 | 2 / 8 | |
| 0.17.1 | 2 / 8 | |
| 0.17.0 | 2 / 8 | |
| 0.16.2 | 2 / 8 | |
| 0.16.1 | 2 / 8 | |
| 0.16.0 | 2 / 8 | |
| 0.15.7 | 2 / 8 | |
| 0.15.5 | 2 / 8 | |
| 0.15.4 | 2 / 8 | |
| 0.15.3 | 2 / 8 | |
| 0.15.1 | 2 / 8 | |
| 0.15.0 | 2 / 8 | |
| 0.14.7 | 2 / 1 | |
| 0.14.6 | 2 / 1 | |
| 0.14.5 | 2 / 1 | |
| 0.14.4 | 2 / 1 | |
| 0.14.3 | 2 / 1 | |
| 0.14.2 | 2 / 1 | |
| 0.14.1 | 2 / 1 | |
| 0.14.0 | 2 / 1 | |
| 0.13.1 | 2 / 1 | |
| 0.13.0 | 2 / 1 | |
| 0.12.1 | 5 / 1 | |
| 0.12.0 | 5 / 1 | |
| 0.11.3 | 5 / 1 | |
| 0.11.2 | 5 / 1 | |
| 0.11.1 | 5 / 1 | |
| 0.11.0 | 5 / 1 | |
| 0.10.0 | 5 / 1 | |
| 0.9.1 | 5 / 1 | |
| 0.9.0 | 5 / 1 | |
| 0.8.4 | 5 / 1 | |
| 0.8.3 | 5 / 1 | |
| 0.8.2 | 5 / 1 | |
| 0.8.1 | 5 / 1 | |
| 0.8.0 | 5 / 1 | |
| 0.7.5 | 5 / 1 | |
| 0.7.4 | 5 / 1 | |
| 0.7.3 | 5 / 1 | |
| 0.7.2 | 5 / 1 | |
| 0.7.1 | 5 / 1 | |
| 0.7.0 | 5 / 1 | |
| 0.6.2 | 5 / 1 | |
| 0.6.1 | 5 / 1 | |
| 0.6.0 | 5 / 1 | |
| 0.3.5 | 3 / 0 | |
| 0.3.4 | 3 / 0 | |
| 0.3.0 | 3 / 0 |
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.