Anything shipped inside an app can be pulled out of it. Pick your own APK, AAB, IPA or Expo export and Ember sniffs it for hardcoded keys, secret EXPO_PUBLIC_ variables and Supabase or Firebase config, right here in your browser.
On a phone? This check works best on a computer. Export your build (EAS: eas build --local or download it from expo.dev; Android Studio: Build › Generate Signed Bundle / APK; Xcode: Product › Archive › Distribute App › Export), then open this page on your computer and pick the file.
Please sign in first. We only show results once we know the app is yours.
What it looks for
Secret keys for OpenAI, Anthropic, Stripe, AWS, GitHub, Supabase and more, using the same rules as our site scan.
EXPO_PUBLIC_ variables with secret names. Expo's docs say these values are visible in plain text in your compiled app.
Supabase service_role keys, which skip every row level security rule.
Supabase and Firebase config. These are public by design, so we list them and point you to the follow-up checks.
What it can't see
Keys your app downloads at runtime, or keys that are encrypted or split up in native code.
Expo inlines EXPO_PUBLIC_ values, so a variable's name may not be in the build. Its value is still checked against the key rules.
Encrypted App Store downloads. Export your own build from Xcode or EAS instead.