hast-util-truncate
hast utility to truncate the tree to a certain number of characters
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): syntax-tree org regularly adds collaborators; wooorm remains the publisher and original author. Maintainer additions here reflect normal org governance, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): wooorm's packages frequently have long gaps between releases; this is a stable utility with no account takeover indicators. | ai | |
| dependencies | unvetted-dep:@types/hast | AI (dependencies): @types/hast is a standard TypeScript type package for the hast ecosystem, used consistently across wooorm's packages. | ai | |
| phantom-deps | phantom-dep:@types/hast | AI (phantom-deps): @types/hast is used for TypeScript type re-exports in the unified ecosystem; not directly imported at runtime by convention. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 3 / 11 | |
| 1.0.2 | 2 / 10 | |
| 1.0.1 | 2 / 12 | |
| 1.0.0 | 2 / 12 |
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.