html5-entities
A table mapping HTML5 entity patterns to unicode code points
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change to aredridel occurred in 2014; aredridel is the listed package author. Legitimate authorship transfer, stable for 10+ years. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): aredridel is the package author per package.json; maintainer addition in 2014 reflects legitimate ownership, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Pure data package with no deps by design; repo URL is present in package.json; sparse README is typical for this era. All bogus-package signals are false positives for this legitimate utility. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4800 days old; provenance attestation was not available at publish time. No security concern. | ai |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsThis version was published by a different npm account than previous versions on 2014-02-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.