strip-bom-buffer
Strip a byte order mark (BOM) from a buffer.
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 | publisher-changed | AI (provenance): Historical 2017 transition from jonschlinkert to phated; phated is a highly reputable publisher with 14k+ approved packages. Legitimate handoff, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical 2017 maintainer transition; phated's track record confirms legitimacy. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): is-utf8 is a well-known, trusted utility; adding it to a BOM-stripping buffer library is semantically appropriate and not suspicious. | ai |
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2017-06-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.