text-encoding (Unlicense OR Apache-2.0) 11 versions

text-encoding

npm Repository Homepage

Polyfill for the Encoding Living Standard's API.

11

Versions

(Unlicense OR Apache-2.0)

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

inexorabletash

Keywords

encodingdecodingliving standard

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is the legitimate published version of this 12-year-old polyfill with 1.5M weekly downloads. Not a throwaway package; this version number is stable and intentional.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this well-established package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from contributor (reyre) to original author (inexorabletash) in 2014; legitimate transition confirmed by package.json authorship and GitHub repo ownership.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): inexorabletash is the original author per package.json and repo owner; adding them as maintainer is expected.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
0.7.0	0 / 0	2018-09-28
0.6.4	0 / 0	2017-01-06
0.6.2	0 / 0	2016-12-29
0.6.1	0 / 0	2016-09-14
0.6.0	0 / 0	2016-04-07
0.5.5	0 / 0	2016-02-25
0.5.2	0 / 0	2014-12-29
0.5.1	0 / 0	2014-12-20
0.5.0	0 / 0	2014-12-14
0.1.0	0 / 0	2014-05-22
0.0.0	0 / 0	2014-04-01

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.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.5

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

2 findings

HIGH Publisher changed: reyre → inexorabletash (on 2014-12-20) provenance

This version was published by a different npm account than previous versions on 2014-12-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.5.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.0

1 finding

LOW No provenance attestation provenance

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

v0.0.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.