Secure app review
We review your project files without executing your code.
LaunchLint only reads relevant files and configuration. We do not install dependencies, run builds, or execute scripts from your project.
No code executionNo npm install, no build, no pod install, and no scripts from your project files. LaunchLint only reads them.
Bounded, safe processingZIPs and GitHub repos are checked for size, file count, paths, and symlinks before the scanner reads relevant files.
Supporting details, not AI guessesSecrets such as API keys are masked. Detected risks point to affected files, traceable details, and official store rules.
What the static check actually examines
LaunchLint looks for signals that matter to Apple and Google Play. It does not evaluate a running app or replace testing on a real device, but it exposes common gaps in project files early.
App configuration and dependenciesLaunchLint reads supported Expo configuration, package.json, and native manifest files to identify platforms, SDKs, and store-relevant settings.
Permissions and privacyThe check compares permissions, purpose strings, tracking signals, and third-party SDKs with details that may need to appear in Privacy Labels or Data Safety.
Login, accounts, and purchasesStatic signals for social login, account creation, account deletion, subscriptions, and in-app purchases are checked for frequent review risks.
Metadata and submissionStore descriptions, support and privacy links, screenshot claims, and test access can be checked alongside the project files and turned into concrete tasks.