utf8
A well-tested UTF-8 encoder/decoder written in JavaScript.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/prettify.js | AI (source-diff): Google code-prettify library bundled with Istanbul coverage output; standard minified dependency, not obfuscated malware. | ai | |
| license | uncommon-license:GPL | AI (license): Dual MIT/GPL licensing is intentional and standard for this author's packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 4 | |
| 2.1.2 | 0 / 7 | |
| 2.1.1 | 0 / 7 | |
| 2.1.0 | 0 / 7 | |
| 2.0.0 | 0 / 6 | |
| 1.0.0 | 0 / 0 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.