stringify-entities
Serialize (encode) 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
stringifyencodeescapehtmlcharacterreferenceentityentities
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:character-entities-html4 | AI (dependencies): character-entities-html4 is a wooorm data package providing HTML4 entity mappings — a natural, benign dependency for an HTML entity encoder. | ai | |
| dependencies | unvetted-dep:character-entities-legacy | AI (dependencies): character-entities-legacy is a wooorm data package providing legacy entity mappings — a natural, benign dependency for an HTML entity encoder. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common (~88% of packages) and not a risk signal for this well-established wooorm package. | ai |
v4.0.3
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.