remark-mdx
remark plugin to support MDX syntax
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:micromark-extension-mdxjs | AI (dependencies): micromark-extension-mdxjs is part of the same mdx-js/mdx monorepo and maintained by the same trusted author (wooorm); not a suspicious dependency for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New Babel deps (@babel/core, plugin-syntax-jsx, helper-plugin-utils, plugin-proposal-object-rest-spread) are canonical packages consistent with remark-mdx's JSX parsing purpose; not suspicious. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): timneutkens was already a listed contributor in package.json before being added as maintainer; this is a legitimate promotion within the mdx-js/mdx project, not a suspicious takeover. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-jsx | AI (phantom-deps): Babel plugins are loaded by convention via @babel/core plugin arrays, not directly imported. This is standard Babel plugin usage for a JSX-processing package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-object-rest-spread | AI (phantom-deps): Babel plugins are loaded by convention via @babel/core plugin arrays, not directly imported. This is standard Babel plugin usage for a JSX-processing package. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): unified is a declared runtime dependency used as plugin infrastructure; not directly imported in source but legitimately required. False positive for this remark plugin pattern. | ai | |
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): remark-parse is a declared runtime dependency used as plugin infrastructure; not directly imported in source but legitimately required. False positive for this remark plugin pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from johno to silvenon occurred in July 2020 and is a documented legitimate maintainer handoff. Silvenon is listed as a contributor in package.json and has a strong track record (314 approved / 0 rejected). | ai | |
| provenance | no-provenance | AI (provenance): wooorm is a well-established npm publisher; lack of provenance is common and not a risk signal for this package. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.3.0 | 2 / 6 | |
| 2.2.1 | 2 / 6 | |
| 2.2.0 | 2 / 6 | |
| 2.1.5 | 2 / 6 | |
| 2.1.4 | 2 / 6 | |
| 2.1.3 | 2 / 6 | |
| 2.1.2 | 2 / 6 | |
| 2.1.1 | 2 / 6 | |
| 2.1.0 | 2 / 6 | |
| 2.0.0 | 2 / 6 | |
| 1.6.22 | 8 / 0 | |
| 1.6.21 | 8 / 0 | |
| 1.6.20 | 8 / 0 | |
| 1.6.19 | 8 / 0 | |
| 1.6.18 | 8 / 0 | |
| 1.6.17 | 8 / 0 | |
| 1.6.16 | 8 / 0 | |
| 1.6.15 | 8 / 0 | |
| 1.6.14 | 8 / 0 | |
| 1.6.13 | 8 / 0 | |
| 1.6.12 | 8 / 0 | |
| 1.6.11 | 8 / 0 | |
| 1.6.10 | 8 / 0 | |
| 1.6.9 | 8 / 0 | |
| 1.6.8 | 8 / 0 | |
| 1.6.7 | 8 / 0 | |
| 1.6.6 | 8 / 0 | |
| 1.6.5 | 8 / 0 | |
| 1.6.4 | 8 / 0 | |
| 1.6.3 | 8 / 0 | |
| 1.6.2 | 8 / 0 | |
| 1.6.1 | 8 / 0 | |
| 1.6.0 | 8 / 0 | |
| 1.5.9 | 8 / 0 | |
| 1.5.8 | 8 / 0 | |
| 1.5.7 | 8 / 0 | |
| 1.5.6 | 8 / 0 | |
| 1.5.5 | 8 / 0 | |
| 1.5.4 | 8 / 0 | |
| 1.5.3 | 8 / 0 | |
| 1.5.2 | 8 / 0 | |
| 1.5.1 | 8 / 3 | |
| 1.5.0 | 8 / 3 | |
| 1.4.5 | 8 / 3 | |
| 1.4.4 | 8 / 3 | |
| 1.4.3 | 8 / 3 | |
| 1.4.2 | 8 / 3 | |
| 1.4.1 | 8 / 3 | |
| 1.4.0 | 8 / 3 | |
| 1.3.2 | 8 / 3 | |
| 1.3.1 | 8 / 3 | |
| 1.3.0 | 8 / 3 | |
| 1.2.2 | 8 / 3 | |
| 1.2.1 | 8 / 3 | |
| 1.1.6 | 7 / 3 | |
| 1.1.5 | 7 / 3 | |
| 1.1.4 | 7 / 3 | |
| 1.1.2 | 7 / 3 | |
| 1.1.1 | 7 / 3 | |
| 1.1.0 | 7 / 3 | |
| 1.0.26 | 7 / 3 | |
| 1.0.25 | 7 / 3 | |
| 1.0.23 | 7 / 3 | |
| 1.0.22 | 7 / 3 | |
| 1.0.21 | 7 / 3 | |
| 1.0.20 | 7 / 3 | |
| 1.0.18 | 7 / 3 | |
| 1.0.15 | 7 / 3 | |
| 1.0.14 | 7 / 3 | |
| 1.0.8 | 7 / 3 | |
| 1.0.2 | 7 / 3 | |
| 1.0.1 | 7 / 3 | |
| 0.20.3 | 7 / 2 | |
| 0.18.2 | 7 / 2 | |
| 0.18.0 | 7 / 2 | |
| 0.17.5 | 7 / 2 | |
| 0.17.4 | 7 / 2 | |
| 0.17.3 | 7 / 2 | |
| 0.17.2 | 3 / 2 | |
| 0.17.1 | 3 / 2 | |
| 0.17.0 | 3 / 2 |
v1.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 finding[Accepted risk] Package 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.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.17.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.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.