@mdx-js/runtime
Deprecated: this package is no longer maintained.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): silvenon (Matija Marohnić) is a listed contributor in package.json and a long-standing member of the mdx-js project. The 2020-07-17 transition is a legitimate maintainer handoff, not a compromise. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 0 / 0 | |
| 1.6.22 | 3 / 0 | |
| 1.6.21 | 3 / 0 | |
| 1.6.20 | 3 / 0 | |
| 1.6.19 | 3 / 0 | |
| 1.6.18 | 3 / 0 | |
| 1.6.17 | 3 / 0 | |
| 1.6.16 | 3 / 0 | |
| 1.6.15 | 3 / 0 | |
| 1.6.14 | 3 / 0 | |
| 1.6.13 | 3 / 0 | |
| 1.6.12 | 3 / 0 | |
| 1.6.11 | 3 / 0 | |
| 1.6.10 | 3 / 0 | |
| 1.6.9 | 3 / 0 | |
| 1.6.8 | 3 / 0 | |
| 1.6.7 | 3 / 0 | |
| 1.6.6 | 3 / 0 | |
| 1.6.5 | 3 / 0 | |
| 1.6.4 | 3 / 0 | |
| 1.6.3 | 3 / 0 | |
| 1.6.2 | 3 / 0 | |
| 1.6.1 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.9 | 3 / 0 | |
| 1.5.8 | 3 / 0 | |
| 1.5.7 | 3 / 0 | |
| 1.5.6 | 3 / 0 | |
| 1.5.5 | 3 / 0 | |
| 1.5.4 | 3 / 0 | |
| 1.5.3 | 3 / 0 | |
| 1.5.2 | 3 / 0 | |
| 1.5.1 | 3 / 11 | |
| 1.5.0 | 3 / 11 | |
| 1.4.5 | 3 / 11 | |
| 1.4.4 | 3 / 11 | |
| 1.4.3 | 3 / 11 | |
| 1.4.2 | 3 / 11 | |
| 1.4.1 | 3 / 11 | |
| 1.4.0 | 3 / 11 | |
| 1.3.2 | 3 / 11 | |
| 1.3.1 | 3 / 11 | |
| 1.3.0 | 3 / 11 | |
| 1.2.2 | 3 / 11 | |
| 1.2.1 | 3 / 11 | |
| 1.1.6 | 3 / 11 | |
| 1.1.5 | 3 / 11 | |
| 1.1.4 | 3 / 11 | |
| 1.1.2 | 3 / 11 | |
| 1.1.1 | 3 / 11 | |
| 1.1.0 | 3 / 11 | |
| 1.0.27 | 3 / 11 | |
| 1.0.26 | 3 / 11 | |
| 1.0.25 | 3 / 11 | |
| 1.0.24 | 3 / 11 | |
| 1.0.23 | 3 / 11 | |
| 1.0.22 | 3 / 11 | |
| 1.0.21 | 3 / 11 | |
| 1.0.20 | 3 / 11 | |
| 1.0.19 | 3 / 11 | |
| 1.0.18 | 3 / 11 | |
| 1.0.16 | 3 / 11 | |
| 1.0.15 | 3 / 11 | |
| 1.0.14 | 3 / 11 | |
| 1.0.10 | 3 / 11 | |
| 1.0.9 | 3 / 11 | |
| 1.0.8 | 3 / 11 | |
| 1.0.7 | 3 / 11 | |
| 1.0.6 | 3 / 11 | |
| 1.0.5 | 3 / 11 | |
| 1.0.4 | 3 / 11 | |
| 1.0.3 | 3 / 11 | |
| 1.0.2 | 3 / 11 | |
| 1.0.1 | 3 / 11 | |
| 0.20.3 | 3 / 11 | |
| 0.20.2 | 3 / 11 | |
| 0.20.1 | 3 / 11 | |
| 0.20.0 | 3 / 11 | |
| 0.19.0 | 3 / 11 | |
| 0.18.2 | 3 / 11 | |
| 0.18.1 | 3 / 11 | |
| 0.18.0 | 3 / 11 | |
| 0.17.5 | 3 / 11 | |
| 0.17.4 | 3 / 11 | |
| 0.17.3 | 3 / 11 | |
| 0.17.0 | 3 / 11 | |
| 0.16.9 | 3 / 11 | |
| 0.16.8 | 3 / 10 | |
| 0.16.6 | 3 / 10 | |
| 0.16.5 | 3 / 10 | |
| 0.16.4 | 3 / 10 | |
| 0.16.3 | 3 / 10 | |
| 0.16.2 | 3 / 10 | |
| 0.16.1 | 3 / 10 | |
| 0.16.0 | 3 / 10 | |
| 0.15.7 | 3 / 10 | |
| 0.15.6 | 3 / 10 | |
| 0.15.5 | 3 / 7 | |
| 0.15.4 | 3 / 7 | |
| 0.15.3 | 3 / 7 |
v1.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
2 findingsThis version was published by a different npm account than previous versions on 2020-07-17. 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.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.