hast-util-excerpt
hast utility to excerpt the tree to a comment
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): kmck is a known contributor in the unified/syntax-tree ecosystem; wooorm regularly adds collaborators. No other risk signals present. | ai | |
| dependencies | unvetted-dep:@types/hast | AI (dependencies): @types/hast is the standard TypeScript type definitions for the hast AST; entirely benign and expected for any hast utility package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): wooorm regularly publishes major version bumps across the unified ecosystem in batches; dormancy between releases is normal for this stable utility package. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): @types/hast is a TypeScript type definition package used by convention in hast utilities; not directly imported but legitimately declared as a dependency. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 2 / 16 | |
| 1.0.2 | 2 / 16 | |
| 1.0.1 | 2 / 19 | |
| 1.0.0 | 2 / 19 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.