← Home

bufferjs

Pure JavaScript Buffer utils.

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

alexbookercoolaj86

Keywords

utilbufferchunkindexOf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from coolaj86 to alexbooker occurred in 2016; this is a historical, stable transition with no adverse signals in 9 years of subsequent use. ai
maintainer-change maintainer-added AI (maintainer-change): alexbooker was added as maintainer in 2016; long-standing legitimate maintainer with clean track record. ai
bogus-package bogus-package AI (bogus-package): Small utility library with no deps is expected; repo URL present in package.json url field; 28k weekly downloads confirms legitimate use. ai

Versions (showing 12 of 12)

Version Deps Published
3.0.1 0 / 0
3.0.0 0 / 0
2.0.0 0 / 0
1.2.1 0 / 0
1.2.0 0 / 0
1.1.0 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0
0.2.3 0 / 0
0.2.1 0 / 0
0.2.0 0 / 0

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

2 findings
HIGH Publisher changed: coolaj86 → alexbooker (on 2016-06-03) provenance

This version was published by a different npm account than previous versions on 2016-06-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.