mdx-bundler
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
kentcdodds
Keywords
mdxbundlermdx-bundleresbuild
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mdx-js/esbuild | AI (dependencies): Core MDX ecosystem package; expected dependency for an MDX bundler. | ai | |
| dependencies | unvetted-dep:remark-mdx-frontmatter | AI (dependencies): Standard remark plugin for MDX frontmatter; appropriate for this package. | ai | |
| dependencies | unvetted-dep:@esbuild-plugins/node-resolve | AI (dependencies): Standard esbuild plugin; expected for bundler functionality. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 10.1.1 | 9 / 24 |
v10.1.1
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.