← Home

rehype-slug

npm Repository Homepage

rehype plugin to add `id` attributes to headings

12
Versions
MIT
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

wooormkmck

Keywords

headinghtmlidpluginrehyperehype-pluginslugunified

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): unified and @types/hast are core ecosystem packages from the same unified org; their addition is expected for a rehype plugin moving to explicit TypeScript typing. ai
provenance no-provenance AI (provenance): wooorm is a highly trusted publisher with a long track record; lack of provenance is a minor gap, not a risk signal for this package. ai
dependencies unvetted-dep:@types/hast AI (dependencies): @types/hast is a standard TypeScript type definition package used throughout the unified/rehype ecosystem; not a runtime risk. ai
phantom-deps phantom-dep:@types/hast AI (phantom-deps): @types/* packages are type-only and never directly imported at runtime; phantom-dep finding is a stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
6.0.0 5 / 9
5.1.0 7 / 11
5.0.1 7 / 12
5.0.0 7 / 12
4.0.1 5 / 11
4.0.0 5 / 11
3.0.0 5 / 9
2.0.3 5 / 9
2.0.2 5 / 9
2.0.1 5 / 8
2.0.0 5 / 8
1.0.0 5 / 8

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
INFO No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
INFO No provenance attestation provenance

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