parse-entities
Parse HTML character references
2
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
wooorm
Keywords
parsehtmlcharacterreferenceentityentities
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:is-decimal | AI (dependencies): is-decimal is a small wooorm utility package in the unified ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:is-hexadecimal | AI (dependencies): is-hexadecimal is a small wooorm utility package in the unified ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:is-alphanumerical | AI (dependencies): is-alphanumerical is a small wooorm utility package in the unified ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:character-entities-legacy | AI (dependencies): character-entities-legacy is a wooorm data package in the unified ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:character-reference-invalid | AI (dependencies): character-reference-invalid is a wooorm data package in the unified ecosystem; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:decode-named-character-reference | AI (dependencies): decode-named-character-reference is a wooorm utility package in the unified ecosystem; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): @types/unist is used as a runtime type export dependency in wooorm's packages; this pattern is intentional and stable. | ai | |
| provenance | no-provenance | AI (provenance): wooorm's packages consistently lack Sigstore provenance; publisher track record and repo metadata provide sufficient trust. | ai |
v4.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.