gatsby-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mime | AI (phantom-deps): mime is declared and used indirectly in Gatsby plugin config; legitimate indirect dependency pattern. | ai | |
| phantom-deps | phantom-dep:pretty-bytes | AI (phantom-deps): pretty-bytes is declared and used indirectly in Gatsby plugin config; legitimate indirect dependency pattern. | ai | |
| phantom-deps | phantom-dep:unist-util-map | AI (phantom-deps): unist-util-map is declared and used indirectly in Gatsby plugin config; legitimate indirect dependency pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the standard Gatsby plugin resolution mechanism; this is intentional and documented behavior for gatsby-mdx. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in mdx-renderer.js is the core MDX runtime evaluation mechanism — intentional design of MDX renderers, not a security risk in this context. | ai | |
| dependencies | unvetted-dep:mdast-util-to-string | AI (dependencies): mdast-util-to-string is a well-known, stable utility in the unified/remark ecosystem; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 0 | |
| 0.6.0 | 25 / 2 | |
| 0.5.2 | 20 / 2 | |
| 0.4.4 | 20 / 2 | |
| 0.3.3 | 19 / 2 | |
| 0.3.2 | 18 / 2 | |
| 0.1.3 | 19 / 2 | |
| 0.0.7 | 12 / 0 | |
| 0.0.6 | 12 / 0 | |
| 0.0.5 | 12 / 0 | |
| 0.0.4 | 11 / 0 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 1 / 0 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.