bytebuffer
The swiss army knife for binary data 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:memcpy | AI (dependencies): memcpy is an optional dependency (native binding optimization), not a hard runtime dep. Consistent with this binary buffer library's purpose and gracefully degrades if absent. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Version 0.0.0 is the legitimate initial release of a 13-year-old package by a known publisher with 68 subsequent versions. Not a throwaway malicious package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require uses path.join(__dirname, 'dist', ...) to load the package's own bundled dist files — not arbitrary external input. Stable false positive for this package. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 1 / 6 | |
| 5.0.0 | 1 / 6 | |
| 4.1.0 | 2 / 6 | |
| 4.0.0 | 2 / 6 | |
| 3.5.5 | 2 / 5 | |
| 3.5.4 | 2 / 5 | |
| 3.5.3 | 2 / 5 | |
| 3.5.2 | 2 / 5 | |
| 3.5.1 | 2 / 5 | |
| 3.5.0 | 2 / 5 | |
| 3.4.0 | 2 / 5 | |
| 3.3.0 | 3 / 5 | |
| 3.2.3 | 3 / 4 | |
| 3.2.2 | 3 / 4 | |
| 3.2.1 | 3 / 4 | |
| 3.2.0 | 3 / 4 | |
| 3.1.1 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.3 | 2 / 3 | |
| 3.0.2 | 2 / 3 | |
| 3.0.1 | 2 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.3.2 | 1 / 3 | |
| 2.3.1 | 1 / 3 | |
| 2.3.0 | 1 / 3 | |
| 2.2.0 | 1 / 3 | |
| 2.1.1 | 1 / 3 | |
| 2.1.0 | 1 / 3 | |
| 2.0.2 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.6.1 | 1 / 3 | |
| 1.6.0 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.4.1 | 1 / 3 | |
| 1.3.8 | 1 / 3 | |
| 1.3.7 | 1 / 3 | |
| 1.3.6 | 1 / 3 | |
| 1.3.5 | 1 / 3 | |
| 1.3.4 | 1 / 3 | |
| 1.3.3 | 1 / 3 | |
| 1.3.2 | 1 / 3 | |
| 1.3.1 | 1 / 3 | |
| 1.3.0 | 1 / 3 | |
| 1.2.3 | 1 / 3 | |
| 1.2.2 | 1 / 3 | |
| 1.2.1 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.5 | 0 / 3 | |
| 1.1.4 | 0 / 3 | |
| 1.1.3 | 0 / 3 | |
| 1.1.2 | 0 / 1 | |
| 1.1.1 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.5 | 0 / 1 | |
| 1.0.4 | 0 / 1 | |
| 1.0.3 | 0 / 1 | |
| 1.0.2 | 0 / 1 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 | |
| 0.9.4 | 0 / 2 | |
| 0.9.3 | 0 / 0 | |
| 0.9.1 | 0 / 0 | |
| 0.9.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.