← Home

mdast-util-visit

npm

Deprecated

3
Versions
—
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

wooorm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Package is an intentional deprecation stub by trusted publisher wooorm; minimal metadata and tiny payload are expected for a tombstone release. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy before a deprecation publish is normal; wooorm is a long-standing trusted publisher with no account-takeover indicators. ai
provenance missing-githead AI (provenance): Deprecation stubs are often published manually outside CI; missing gitHead is expected and not a risk signal for this package. ai

Versions (showing 3 of 3)

Version Deps Published
0.2.0 0 / 0
0.1.1 0 / 11
0.1.0 0 / 11

v0.2.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wooorm.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

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.