← Home

rehype-infer-description-meta

npm Repository Homepage

rehype plugin to infer file metadata from the document

4
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

descriptionexcerptfilehasthtmlmetapluginrehyperehype-pluginsummarytruncateunified

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@types/hast AI (dependencies): @types/hast is a standard DefinitelyTyped type package used throughout the unified/rehype ecosystem; no security risk. ai
maintainer-change maintainer-added AI (maintainer-change): kmck added as maintainer in the unified/rehypejs ecosystem; wooorm is a highly trusted publisher and this is a collaborative org-level addition. ai
publish-pattern dormant-publish AI (publish-pattern): wooorm is a highly trusted publisher; dormancy followed by a major version bump is consistent with deliberate maintenance, not account takeover. ai
publish-pattern new-deps-added AI (publish-pattern): vfile is a core unified ecosystem package also maintained by wooorm; adding it to a rehype plugin is expected and benign. ai
phantom-deps phantom-dep:unified AI (phantom-deps): unified is used as a peer/type dependency in the unified ecosystem; phantom detection is a stable false positive for this package. ai
phantom-deps phantom-dep:@types/hast AI (phantom-deps): @types/hast is used for TypeScript type re-exports, not direct runtime imports; phantom detection is a stable false positive here. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.0 8 / 11
1.1.0 7 / 14
1.0.1 7 / 14
1.0.0 7 / 14

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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