← Home

bare-buffer

11
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 11 of 11)

Version Deps Published
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

v3.6.1

2 findings
HIGH Publisher changed: kasperisager → GitHub Actions (on 2026-06-01) provenance

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

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.5.0

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.4.4

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.4.3

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.4.2

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.4.1

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.4.0

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.3.1

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.3.0

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.

v3.2.0

2 findings
HIGH Bundled binary files (13) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/android-arm/bare-buffer.bare • prebuilds/android-arm64/bare-buffer.bare • prebuilds/android-ia32/bare-buffer.bare • prebuilds/android-x64/bare-buffer.bare • prebuilds/darwin-arm64/bare-buffer.bare • prebuilds/darwin-x64/bare-buffer.bare • prebuilds/ios-arm64-simulator/bare-buffer.bare • prebuilds/ios-arm64/bare-buffer.bare • prebuilds/ios-x64-simulator/bare-buffer.bare • prebuilds/linux-arm64/bare-buffer.bare ... and 3 more

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.