← Home

bare-buffer

19
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mafintosh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance slsa-provenance AI (provenance): Holepunch org consistently publishes via GitHub Actions CI with SLSA attestation; stable pattern for this package. ai
npm-metadata bundled-binaries AI (npm-metadata): Native addon package; prebuilds are the documented distribution mechanism for this package. ai
semgrep semgrep:base64-decode AI (semgrep): atob() implementation using Buffer.from with base64 encoding — standard API, not malicious. ai

Versions (showing 19 of 19)

Version Deps Published
3.6.2 0 / 6
3.6.1 0 / 6
3.6.0 0 / 5
3.5.0 0 / 5
3.4.4 0 / 5
3.4.3 0 / 5
3.4.2 0 / 5
3.4.1 0 / 5
3.4.0 0 / 5
3.3.1 0 / 5
3.3.0 0 / 5
3.2.0 0 / 5
3.1.4 0 / 5
3.1.3 0 / 5
3.1.2 0 / 5
3.1.0 0 / 5
3.0.2 0 / 5
3.0.1 0 / 5
3.0.0 0 / 5

v3.6.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

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

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.