he MIT 27 versions

he

npm Repository Homepage

A robust HTML entities encoder/decoder with full Unicode support.

27

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

mathias

Keywords

stringentitiesentityhtmlencodedecodeunicode

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:pg	AI (typosquat): 'he' is a well-established HTML entity library by Mathias Bynens, not a typosquat of 'pg'. Short package names legitimately trigger Levenshtein matches.	ai	2026/04/24
typosquat	typosquat.levenshtein:qs	AI (typosquat): 'he' is a well-established HTML entity library by Mathias Bynens, not a typosquat of 'qs'. Short package names legitimately trigger Levenshtein matches.	ai	2026/04/24
semgrep	semgrep:eval-usage	AI (semgrep): eval() in src/data.js is used in a build-time data generation script to sort known Unicode entity strings — not user-supplied input. Legitimate use in this well-known HTML entity library.	ai	2026/04/24
provenance	missing-githead	AI (provenance): he is a long-established package by a trusted publisher; missing gitHead is a metadata artifact of older publish tooling, not a malicious indicator.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance attestation; absence is expected for this era of publishing and does not indicate risk for this well-known package.	ai	2026/04/24

Versions (showing 27 of 27)

Version	Deps	Published
1.2.0	0 / 14	2018-09-23
1.1.1	0 / 12	2017-01-23
1.1.0	0 / 12	2016-05-06
1.0.0	0 / 12	2016-04-05
0.5.0	0 / 12	2014-08-24
0.4.1	0 / 12	2014-05-24
0.4.0	0 / 11	2014-05-23
0.3.6	0 / 10	2013-08-07
0.3.5	0 / 10	2013-08-04
0.3.4	0 / 10	2013-08-02
0.3.3	0 / 10	2013-07-30
0.3.2	0 / 10	2013-07-27
0.3.1	0 / 10	2013-07-01
0.3.0	0 / 10	2013-07-01
0.2.1	0 / 10	2013-06-28
0.2.0	0 / 10	2013-06-27
0.1.10	0 / 10	2013-06-27
0.1.9	0 / 10	2013-06-27
0.1.8	0 / 11	2013-06-27
0.1.7	0 / 11	2013-06-27
0.1.6	0 / 11	2013-06-27
0.1.5	0 / 11	2013-06-26
0.1.4	0 / 11	2013-06-26
0.1.3	0 / 11	2013-06-26
0.1.2	0 / 11	2013-06-25
0.1.1	0 / 11	2013-06-25
0.1.0	0 / 11	2013-06-25

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mathias.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.