← Home

@mdx-js/loader

Webpack loader for MDX

100
Versions
MIT
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

johnotimneutkenswooormremcohaszing

Keywords

jsxmarkdownmdxpreactreactremarkvuewebpack

Versions (showing 100 of 133)

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 / 12
2.2.1 2 / 12
2.2.0 2 / 12
2.1.5 2 / 12
2.1.4 2 / 12
2.1.3 2 / 12
2.1.2 2 / 12
2.1.1 2 / 12
2.1.0 2 / 12
2.0.0 2 / 12
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 / 8
1.5.0 3 / 8
1.4.5 3 / 8
1.4.4 3 / 8
1.4.3 3 / 8
1.4.2 3 / 8
1.4.1 3 / 8
1.4.0 3 / 8
1.3.2 3 / 8
1.3.1 3 / 8
1.3.0 3 / 8
1.2.2 3 / 8
1.2.1 3 / 8
1.1.6 3 / 8
1.1.5 3 / 8
1.1.4 3 / 8
1.1.2 3 / 8
1.1.1 3 / 8
1.1.0 3 / 8
1.0.27 3 / 8
1.0.26 3 / 8
1.0.25 3 / 8
1.0.24 3 / 8
1.0.23 3 / 8
1.0.22 3 / 8
1.0.21 3 / 8
1.0.20 3 / 8
1.0.19 3 / 8
1.0.18 3 / 8
1.0.16 3 / 8
1.0.15 3 / 8
1.0.14 3 / 8
1.0.10 3 / 8
1.0.9 3 / 8
1.0.8 3 / 8
1.0.7 3 / 8
1.0.6 3 / 8
1.0.5 3 / 8
1.0.4 3 / 8
1.0.3 3 / 8
1.0.2 3 / 8
1.0.1 3 / 8
0.20.3 3 / 8
0.20.2 3 / 8
0.20.1 3 / 8
0.20.0 3 / 8
0.19.0 3 / 8
0.18.2 3 / 8
0.18.1 3 / 8
0.18.0 3 / 8
0.17.5 3 / 8
0.17.4 3 / 8
0.17.3 3 / 8
0.17.0 3 / 8
0.16.8 3 / 8
Showing 100 of 133 Next page →

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: johno → wooorm (on 2022-02-01) provenance

This version was published by a different npm account than previous versions on 2022-02-01. 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.