@mintlify/mdx
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): Scoped @mintlify org package; levenshtein match to 'mobx' is a false positive. No impersonation intent — this is a Markdown/MDX parser from an established org. | ai | |
| phantom-deps | phantom-dep:mdast-util-mdx-jsx | AI (phantom-deps): mdast-util-mdx-jsx is explicitly declared as a direct dependency in package.json; phantom-dep finding is a false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 16 / 21 | |
| 3.0.4 | 16 / 21 | |
| 3.0.3 | 16 / 21 | |
| 3.0.2 | 16 / 21 | |
| 3.0.1 | 15 / 21 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.