← Home

mdx-utils

npm
5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

biscarch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Package is a legitimate MDX utility by a well-established publisher (biscarch) with 4.5k weekly downloads and 6 versions. Metadata gaps reflect an early 0.0.1 release, not spam or malice. ai
npm-metadata no-description AI (npm-metadata): Missing description is a metadata quality issue in this early release; package is legitimate and well-established in the MDX ecosystem. ai

Versions (showing 5 of 5)

Version Deps Published
0.2.0 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.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.