quickbit-native
libquickbit JavaScript bindings for Node.js
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): Prebuilt platform binaries are expected for this native addon; source code (binding.cc, CMakeLists.txt) is included and repo is public. Standard Holepunch/Bare addon pattern. | ai | |
| dependencies | unvetted-dep:require-addon | AI (dependencies): require-addon is the standard Holepunch utility for loading native addons; its use is expected and appropriate for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.4.8 | 1 / 8 | |
| 2.4.7 | 1 / 8 | |
| 2.4.6 | 1 / 8 | |
| 2.4.5 | 1 / 8 | |
| 2.4.4 | 1 / 8 | |
| 2.4.3 | 1 / 7 |
v2.4.8
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/android-arm/quickbit-native.bare • prebuilds/android-arm64/quickbit-native.bare • prebuilds/android-ia32/quickbit-native.bare • prebuilds/android-x64/quickbit-native.bare • prebuilds/darwin-arm64/quickbit-native.bare • prebuilds/darwin-x64/quickbit-native.bare • prebuilds/ios-arm64-simulator/quickbit-native.bare • prebuilds/ios-arm64/quickbit-native.bare • prebuilds/ios-x64-simulator/quickbit-native.bare • prebuilds/linux-arm64/quickbit-native.bare ... and 13 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.