← Home

bops

npm Repository Homepage

buffer operations

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

chrisdickinson

Keywords

bufferoperationsbinary

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): bops (buffer operations) is a 13-year-old legitimate package with 834k weekly downloads; the name similarity to cors is coincidental and not an impersonation attempt. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() in read.js is used to generate typed buffer accessor methods from internally-controlled key names — a legitimate, transparent optimization pattern stable across versions of this package. ai
publish-pattern dormant-publish AI (publish-pattern): Long dormancy is consistent with a mature, stable utility library. Publisher has a clean 143/0 track record and the version diff shows no material changes. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.1 2 / 1
1.0.0 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1
0.0.7 2 / 1
0.0.6 2 / 1
0.0.5 2 / 1
0.0.4 2 / 1
0.0.3 2 / 1
0.0.2 2 / 1
0.0.1 2 / 1

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

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.

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.