bare-buffer
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 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.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.