@rspress/mdx-rs
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
chenjiahan
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Standard napi-rs loader pattern: runs 'which ldd' to detect musl vs gnu Linux for native binary selection. Hardcoded, benign, no user input or network involved. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): Same napi-rs musl detection pattern — execSync('which ldd') is a hardcoded, safe command used only to identify the Linux libc variant for binary loading. | ai | |
| provenance | no-provenance | AI (provenance): Established package (946 days, 24 versions) from a trusted publisher; lack of provenance attestation is common and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.6.6 | 0 / 12 |
v0.6.6
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.