Remove a byte order mark (BOM) from a buffer.
62%
Total Score
50
100
93
75
50
No build provenance attestation or trusted-publisher information is present. This limits publication transparency, but it is not by itself evidence that the release is unsafe to depend on.
The package has had no registry release in about nine years, with all three releases concentrated in June and July 2017. This is a meaningful maintenance concern for a dependency, although the package is a small, stable utility.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. That lowers confidence in ongoing maintenance rather than making this simple utility unusable on its own.
The repository has no security policy. This is a transparency and reporting gap, but it is less significant for a small, narrowly scoped utility than for a security-sensitive package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
is-utf8 Version ^0.2.1 | — | — |
is-buffer Version ^1.1.5 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.