@callstack/repack
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
Keywords
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): CMake build intermediates (.bin/.o) from Android native module compilation; expected for React Native native libraries. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): Scoped @callstack package; legitimate org, not a typosquat of react. | ai | |
| typosquat | typosquat.levenshtein:webpack | AI (typosquat): Scoped @callstack package; legitimate org, not a typosquat of webpack. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.2.5 | 25 / 26 |
v5.2.5
2 findingsPackage contains compiled binaries that could be backdoors: • android/.cxx/Debug/3a5t1l4q/arm64-v8a/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_C.bin • android/.cxx/Debug/3a5t1l4q/armeabi-v7a/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_C.bin • android/.cxx/Debug/3a5t1l4q/x86_64/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_C.bin • android/.cxx/Debug/3a5t1l4q/x86/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_C.bin • android/.cxx/Debug/3a5t1l4q/arm64-v8a/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_CXX.bin • android/.cxx/Debug/3a5t1l4q/armeabi-v7a/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_CXX.bin • android/.cxx/Debug/3a5t1l4q/x86_64/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_CXX.bin • android/.cxx/Debug/3a5t1l4q/x86/CMakeFiles/3.22.1-g37088a8/CMakeDetermineCompilerABI_CXX.bin • android/.cxx/Debug/3a5t1l4q/arm64-v8a/CMakeFiles/3.22.1-g37088a8/CompilerIdC/CMakeCCompilerId.o • android/.cxx/Debug/3a5t1l4q/armeabi-v7a/CMakeFiles/3.22.1-g37088a8/CompilerIdC/CMakeCCompilerId.o ... and 14 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.