rehype-highlight
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
wooormkmckremcohaszing
Keywords
hasthighlightinghighlighthtmlpluginrehype-pluginrehypesyntaxunified
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/hast | AI (dependencies): @types/hast is a DefinitelyTyped type-definition package used legitimately for TypeScript type declarations in this hast-ecosystem package; not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): @types/* packages provide type information and are not directly imported at runtime; phantom-dep firing on them is a stable false positive for TypeScript packages. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 5 / 11 |
v7.0.2
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.