← Home

butils

npm Repository Homepage

helper functions to make buffers faster

8
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

nlf

Keywords

bufferctype

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from nathan-lafreniere to nlf in 2013 is a historical account rename; both identities belong to Nathan LaFreniere as confirmed by package.json author field and repo URL. ai
maintainer-change maintainer-added AI (maintainer-change): Same historical rename event from 2013; nlf is the same author as nathan-lafreniere. Stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.0 0 / 3
0.0.7 0 / 2
0.0.6 0 / 2
0.0.5 0 / 2
0.0.4 0 / 2
0.0.3 0 / 1
0.0.2 0 / 0
0.0.1 0 / 0

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

2 findings
HIGH Publisher changed: nathan-lafreniere → nlf (on 2013-08-08) provenance

This version was published by a different npm account than previous versions on 2013-08-08. 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.

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.