- Home
- Skills
- Mobile Development
- Expo EAS Config Check
More screenshots
Works with the AI Agents you already use
Expo EAS Config Check
puts your OpenAI key in plain text inside every copy of your app, because Expo copies each EXPO_PUBLIC_ value your code reads into the JavaScript bundle.
$5
Expo EAS Config Check
Example session with this skill installed
Check this project with expo-eas-config-check.
- Read your context and instructions
- Compiled the expo eas config
$ python3 scripts/check_expo.py examples/risky
BLOCK apps/mobile/.env.production:4 E01 SECRET_IN_PUBLIC_ENV_VAR
EXPO_PUBLIC_OPENAI_API_KEY=<redacted>
Why: An EXPO_PUBLIC_ variable holds a secret: its value has the shape of a secret key (a Stripe secret key, an OpenAI or GitHub token, a Supabase service_role key and similar), its name ends in a secret word (_SECRET, _SECRET_KEY, _PASSWORD, _PRIVATE_KEY, SERVICE_ROLE_KEY, AUTH_TOKEN), or it is the API key of a provider whose keys are server-only (OpenAI, Anthropic, Gemini, Twilio and similar). The prefix marks a value for the app: Expo replaces each process.env.EXPO_PUBLIC reference in your code with the value in the JavaScript bundle, where anyone who has the app can read it in plain text.
Safer: Drop the EXPO_PUBLIC prefix and keep the secret on a server (your API, an Expo Router API route or a cloud function) that the app calls. Rotate the key: it may already be in published builds and updates.
BLOCK apps/mobile/app.json:11 E06 UPDATE_URL_PLAIN_HTTP
BLOCK apps/mobile/app.json:12 E07 ANTI_BRICKING_DISABLED
BLOCK apps/mobile/app.json:32 E02 SECRET_IN_APP_CONFIG
BLOCK apps/mobile/app/chat.tsx:11 E01 SECRET_IN_PUBLIC_ENV_VAR
BLOCK apps/mobile/credentials.json:5 E04 SIGNING_CREDENTIALS_NOT_IGNORED
BLOCK apps/mobile/eas.json:16 E05 DEV_BUILD_IN_RELEASE_PROFILE
BLOCK apps/mobile/eas.json:20 E03 SECRET_IN_EAS_JSON
BLOCK apps/mobile/lib/supabase.ts:6 E01 SECRET_IN_PUBLIC_ENV_VAR
REVIEW apps/kiosk/app.config.ts:10 E13 SELF_HOSTED_UPDATES_UNSIGNED
REVIEW apps/kiosk/app.config.ts:10 E14 UPDATES_WITHOUT_RUNTIME_VERSION
REVIEW apps/kiosk/app.config.ts:11 E18 ANTI_BRICKING_IN_DYNAMIC_CONFIG
REVIEW apps/kiosk/app.config.ts:15 E17 SERVER_ENV_COPIED_INTO_APP_CONFIG
REVIEW apps/mobile/.env.production:5 E16 KEY_SHIPPED_LOOKS_PRIVATE
REVIEW apps/mobile/app.json:8 E19 LEGACY_ARCH_OPT_OUT_IGNORED
REVIEW apps/mobile/app.json:18 E12 ATS_DISABLED
REVIEW apps/mobile/app.json:27 E15 SECURE_STORE_DATA_IN_BACKUP
REVIEW apps/mobile/app.json:28 E11 CLEARTEXT_TRAFFIC_ALLOWED
REVIEW apps/staff/app.json:8 E20 UPDATE_URL_NOT_HTTPS
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 8 files, 8 with Expo/EAS content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
EXPO_PUBLIC_OPENAI_API_KEY=... puts your OpenAI key in plain text inside every copy of your app, because Expo copies each EXPO_PUBLIC_ value your code reads into the JavaScript bundle. A production build profile with "developmentClient": true sends the development client to store users, and "disableAntiBrickingMeasures": true in app.json turns off the update safety net for every build, production included. This skill finds those and fourteen other Expo and EAS configuration mistakes before you ship, and tells you how to fix each one.
Your agent runs a scanner on app.json, app.config.js and app.config.ts, eas.json (comments and trailing commas are fine), credentials.json, .env files, package.json and .gitignore, and on the process.env.EXPO_PUBLIC_ references in your JavaScript and TypeScript code. It knows which parts of the app config Expo keeps out of the public config, follows eas.json profiles through extends, reads .gitignore rules the way git does, tells publishable client keys (Firebase, Supabase, Stripe and Clerk publishable keys, RevenueCat, Mapbox, PostHog) from secret ones, and works across monorepos with several apps. It never runs Expo, EAS CLI, your app config or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- E01: an EXPO_PUBLIC_ variable that holds a secret (in .env files, eas.json build env or code): a value with the shape of a secret key (Stripe secret keys, OpenAI, Anthropic, GitHub, AWS, a Supabase service_role key and others), a name that ends in _SECRET, _SECRET_KEY, _PASSWORD, _PRIVATE_KEY, _SERVICE_ROLE_KEY or _AUTH_TOKEN, or the API key of a server-only AI, email or SMS provider such as EXPO_PUBLIC_OPENAI_API_KEY (storage-key names such as EXPO_PUBLIC_AUTH_TOKEN_STORAGE_KEY are not flagged)
- E02: a secret in app.json or app.config: a secret-shaped value or a literal password or secret setting in extra, plugin options or hooks, a password in a URL, or ...process.env spread into the config
- E03: a secret in eas.json: a build profile env variable whose name ends in a secret phrase (or is a server-only provider key) set to a literal, an API key or token name set to a long generated value, or any secret-shaped value
- E04: credentials.json, a keystore or distribution certificate it names, an App Store Connect or Google Play key that eas.json submit names, or the expo-updates code signing private key, in the project with no .gitignore rule covering it
- E05: a production, release or store build profile (not internal) that makes a development build: developmentClient true (also through extends), a Debug iOS build configuration or a Debug Gradle command
- E06: updates.url over plain http to a public host, unsigned, in an app config that also allows plain http (usesCleartextTraffic or NSAllowsArbitraryLoads)
- E07: disableAntiBrickingMeasures true in app.json, which applies to every build
REVIEW
- E11: usesCleartextTraffic true (expo-build-properties)
- E12: NSAllowsArbitraryLoads true in ios.infoPlist (App Transport Security off)
- E13: a self-hosted updates server without updates.codeSigningCertificate
- E14: updates.url set but no runtimeVersion, so expo-updates stays disabled
- E15: expo-secure-store with configureAndroidBackup false while Android backups are allowed
- E16: an EXPO_PUBLIC_ variable or app config value named like an API key that holds a long generated literal that is not a known publishable key
- E17: app.config copying a secret or API key environment variable (such as OPENAI_API_KEY) into extra or plugin options, where it ships with the app
- E18: disableAntiBrickingMeasures true written in app.config
- E19: newArchEnabled false on Expo SDK 55 or later, where the setting is ignored
- E20: any other plain-http updates.url to a host that is not local: iOS and Android 9 and later refuse it by default, so updates usually fail
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official Expo or Apple documentation link for each rule
- A risky and a safe example monorepo (three apps), and the real report the scanner produces on the risky one
Limits It reads file text and never runs app.config.js or app.config.ts, so values built by functions or imports are not followed, and environment variables are judged by their names, not their values. E04 decides from .gitignore text, not from git history, so a file that is already committed is not detected. EAS environment variables stored on Expo's servers are not checked, and EAS Update projects without code signing are not reported because Expo offers code signing for EAS Update only on paid plans. Native ios and android files are not read. The official custom-expo-updates-server example client allows cleartext for its localhost server and is reported as E11 REVIEW on purpose. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Static check of config and code text. App config code is not run, secrets are found by name and key format, and git history is not read. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
- expo-updates
Node.jsexpo
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example projects include clearly fake, inert keys and passwords (not-a-real-..., NOTREAL...) for the scanner to find. Nothing is run.