Free configuration check
Check app.json and package.json for a few common App Store risk signals. Runs locally in your browser with no login or code execution.
Local in your browser · nothing stored
Free tool
The Expo checker reads pasted `app.json` and `package.json` content locally in the browser and shows at most three notable permission, authentication, purchase, or tracking signals. It executes no code and does not claim to know the final native artifact.
Expo configuration contains identity, plugins, purpose strings, and Android permissions. `package.json` exposes direct dependencies that may introduce data flows or store duties.
An auth, purchase, or analytics package is not automatically a defect. It prompts a check of sign-in alternatives, deletion, in-app purchase rules, App Privacy, and Data Safety.
Use the planned production configuration, not a tutorial project. Remove secrets, private endpoints, and personal test data. If `app.config.ts` creates values dynamically, export a redacted resolved configuration or use the full repository review.
Development, preview, and production can carry different identifiers, plugins, and permissions. A clean development build does not prove the store artifact.
The tool deliberately returns only a few prioritized observations. A missing camera purpose string is more direct than an SDK whose data use depends on configuration.
Verify every observation in the source and the resolved native configuration because plugins can add or override values.
The full static review connects supported configuration, manifests, source signals, listing data, and direct dependencies. It can name affected files and generate tasks for Codex, Cursor, or Claude Code.
Readiness score, complete supporting evidence, every finding, repeat reviews, and the submission package remain part of the paid project review.