utf-8-validate
Check if a buffer contains valid UTF-8
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~12% adoption); not a concern for this well-established package. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard install mechanism for native addons with prebuilt binaries; stable for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for multiple platforms are standard practice for native addons using prebuildify. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is the standard prebuildify runtime loader; expected dependency for native addons. | ai |
v6.0.6
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-x64/utf-8-validate.musl.node • prebuilds/darwin-arm64/utf-8-validate.node • prebuilds/darwin-x64/utf-8-validate.node • prebuilds/linux-x64/utf-8-validate.node • prebuilds/win32-ia32/utf-8-validate.node • prebuilds/win32-x64/utf-8-validate.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/linux-x64/utf-8-validate.musl.node • prebuilds/linux-x64/utf-8-validate.node • prebuilds/win32-ia32/utf-8-validate.node • prebuilds/win32-x64/utf-8-validate.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.