
Security Fundamentals
Turtles, Clams, and Cyber Threat Actors: Shell Usage
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
react-native-app-integrity-checksum
Advanced tools
The library supports the VAPT requirement called app integrity. The library can generate a unique checksum based on the files of your react native application source code. It mainly focuses to React Native JS bundle file changes.
The library supports the VAPT requirement called app integrity. The library can generate a unique checksum based on the files of your react native application source code. It mainly focuses to React Native JS bundle file changes.
npm install react-native-app-integrity-checksum
The current implementation of the library (For IOS) is to only detect JS bundle changes and generating a unique hash key when there are changes.
your project directory -> ios -> podfile -> under the target
pod "AWFileHash"
then run,
pod install
npx react-native bundle --entry-file='index.js' --bundle-output='./ios/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'
This will generate the relevant bundle file in your project, ios folder.
(bundle will be generated usually inside of the ios folder. when adding the file, please tick on copy if items needed)
https://images2.imgbox.com/84/1b/1RQiTMWo_o.png
The current implementation of the library (For Android) is to detect the JS bundle changes and as well the native source code changes. It also generates a unique hash key when there are changes.
1). First, you have to create an assets folder under the main folder.
your project directory -> android -> app -> src -> main -> assets
https://images2.imgbox.com/52/a3/uA4nRdyK_o.png
If you have this folder already, you are good to go.
2). Run the below command to generate the bundle file manually. When you are in production, this will create automatically.
npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
Now you can see the android bundle file inside the previously created assets folder.
import { getChecksum } from 'react-native-app-integrity-checksum';
// ...
const result = await getChecksum();
In development mode, when you are doing the source code changes, the previously generated JS bundle will not be changed. You have to generate it manually once you have done the changes. But production mode will automatically generate it when building the application.
If the library does not return anything, you need to follow the steps previously defined. This happenes when missing the JS bundle file.
Try with the given example application. If not it works, Please open an Issue.
See the contributing guide to learn how to contribute to the repository and the development workflow.
MIT
Made with create-react-native-library
FAQs
The library supports the VAPT requirement called app integrity. The library can generate a unique checksum based on the files of your react native application source code. It mainly focuses to React Native JS bundle file changes.
The npm package react-native-app-integrity-checksum receives a total of 4 weekly downloads. As such, react-native-app-integrity-checksum popularity was classified as not popular.
We found that react-native-app-integrity-checksum demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security Fundamentals
The Socket Threat Research Team uncovers how threat actors weaponize shell techniques across npm, PyPI, and Go ecosystems to maintain persistence and exfiltrate data.
Security News
At VulnCon 2025, NIST scrapped its NVD consortium plans, admitted it can't keep up with CVEs, and outlined automation efforts amid a mounting backlog.
Product
We redesigned our GitHub PR comments to deliver clear, actionable security insights without adding noise to your workflow.