Keep your React Native app shippable.

One command tells you whether your app can still upgrade and still ship: unsupported versions, New Architecture blockers, Google Play deadlines, setups that crash at runtime, performance traps, buttons screen readers cannot name, and security holes from leaked keys to vulnerable dependencies.

npx nativekeel

Free and open source. No signup. Your code never leaves your machine.
Check a package.json in your browser → · See a sample report

Works with GitHub Actions · SonarQube · Claude Code, Codex and Cursor

Listed on React Native Directory · the official MCP Registry · Glama · GitHub Marketplace · awesome-mcp-servers

NativeKeel health report  acme-app
React Native 0.77.1 (latest 0.88.0)
New Architecture  android: off  ios: off

✖ CRITICAL React Native 0.77.1 is no longer supported
           You are 11 minor versions behind.
✖ CRITICAL New Architecture is disabled
           Cannot upgrade past 0.81 until it migrates.
✖ CRITICAL AWS access key ID shipped inside the app
           Anyone who downloads the app can extract it.
▲ HIGH     iOS AppDelegate is missing RCTAppDependencyProvider
           A launch crash in Release once the New Architecture is on.

Summary  4 critical · 4 high · 6 medium · 6 low
Ratings  Security E · Store E · Stability A
         Upgrade E · Performance A · Accessibility C

Start here
  1. Revoke the AWS access key ID in src/App.js:6 today.
  2. Set targetSdkVersion = 36 in android/build.gradle.
  3. Replace push-notification-ios (no New Architecture).

Before you upgrade, ask it

npx nativekeel upgrade reads your code and dependencies and tells you, with file and line, what breaks on the newest React Native or Expo. This is its real output on a sample app.

npx nativekeel upgrade on a React Native 0.84 app: NOT READY, 3 blockers in its own code (StyleSheet.absoluteFillObject removed in 0.85, InteractionManager removed in 0.87, StatusBar translucent removed in 0.87), each with file, line and the fix.

“Instead of waiting for build-time errors to break our pipeline, it immediately flagged upcoming blockers. It didn’t just tell me what was broken. It generated an actionable blueprint to prioritize and patch every single issue systematically.”

Sahith Chary, Software Developer, preparing a React Native app for Xcode 27

In use

725npm downloads, last 7 days
21,586since launch, 4 Oct 2026
17 Oct: 1,76818 Oct: 1,09819 Oct: 020 Oct: 021 Oct: 1,09122 Oct: 57723 Oct: 1,18724 Oct: 57325 Oct: 13826 Oct: 5727 Oct: 20728 Oct: 93829 Oct: 7530 Oct: 5331 Oct: 2391 Nov: 2182 Nov: 1293 Nov: 514 Nov: 495 Nov: 636 Nov: 377 Nov: 348 Nov: 2459 Nov: 7810 Nov: 20311 Nov: 17412 Nov: 5713 Nov: 4814 Nov: 11715 Nov: 48
Daily downloads through 15 Nov

From npm's public download counts, which include CI runs and package mirrors. NativeKeel sends no telemetry, so we do not know more than this.

From a real upgrade

The App Store rejected a release for a launch crash. The fix that shipped only hid it.

The real cause was one line missing from the iOS AppDelegate since React Native 0.77. On Android, an audio library stopped the app from starting at all, with the process still alive. Neither shows up in a debug build on your machine.

  • Both are now checks. Run on the original repository, NativeKeel flags them before any work starts.
  • So are 5 of the 7 other things that broke on the way to 0.80, from Podfile leftovers to a patch that silently stopped applying.
Read the case study
14problems fixed
0.77 → 0.80React Native, React 19
5native modules removed
~2 hengineering time

What it checks

111 checks and 17 secret patterns for the problems that quietly turn a routine update into a three-week project, found in seconds. Tuned on 850+ open-source React Native and Expo apps, with recently updated ones added every week, to keep false alarms out (measured accuracy and blind spots) (what we found in them). Outputs for terminal, HTML, Markdown, JSON, GitHub code scanning (SARIF) and SonarQube.

Versions

Support status

React Native supports only the latest three minors. Expo moves just as fast. Know where you stand before a store deadline decides for you.

Architecture

New Architecture blockers

The legacy architecture is gone since 0.82. See which native modules block the switch, which library versions match each React Native release, and what to replace, including libraries whose iOS code no longer compiles on React Native 0.87.

Store

Google Play and App Store rules

Xcode 27's UIScene requirement (the app does not launch without it; App Store uploads need it from April 2027), target SDK, permissions Google Play restricts, account deletion and Sign in with Apple, the iOS privacy manifest and SDKs too old to have one, and 16 KB pages: it opens your built APK or AAB and measures the alignment of every native library.

Security

Secrets and signing keys

API keys shipped in the bundle, AI provider keys (OpenAI, Gemini, Anthropic, Groq…) read from EXPO_PUBLIC_ or .env variables, .env values compiled into the app, keys added at build time (it opens the built APK, AAB or IPA, Hermes bytecode included), committed keystores, signing passwords and App Store Connect keys. 12 of 869 apps ship an AI key →

Security

Could someone steal data or abuse your app?

Firebase rules open to anyone or granting writes to every signed-in user, Supabase tables without row level security or with unconditional row policies, backend admin credentials compiled into the app (Supabase service_role, Hasura admin secret, Firebase service accounts, database passwords), TLS certificate checks turned off in native code, hardcoded encryption keys and weak hashing, passwords, session tokens and API keys in release logs or plain storage (redux-persist included), recovery phrases and private keys copied to the clipboard, keychain items readable while the device is locked, unsafe WebViews, URLs trusted after a text comparison (url.startsWith('https://site.com') also accepts site.com.attacker.dev), subscriptions or roles the app writes to its own database, login tokens sent to other sites by a global axios interceptor, Android components any app can start, deep links other apps can intercept, plain-HTTP API calls, source maps shipped in the app, GitHub Actions workflows that run a fork's pull request with your secrets (pull_request_target) or paste an issue or pull request title into a script, known malware anywhere in your lockfile's dependency tree (supply-chain attacks such as the Shai-Hulud worm), a critical Metro development-server command injection (CVE-2025-11953, actively exploited) from a vulnerable @react-native-community/cli in your lockfile even when it is only a transitive dependency, and known vulnerabilities in the exact versions you ship. New checks trace credential leaks and external input reaching eval or SQL, inspect OAuth settings and broad private file-sharing paths. Native Android checks follow archive paths into writes and incoming Intent data into component launches, WebViews, SQL and filesystem paths. Run npx nativekeel security for evidence, prerequisites and fixes. Security checks and coverage →

Stability

Crash risks

Setups that build fine and crash at runtime: packages that are not the versions your Expo SDK was tested with, release builds still pointing at a development server, libraries that need a newer React Native than you have, Reanimated without its Babel plugin or worklets, mixed Firebase or React Navigation majors, a second copy of React inside a dependency, native modules that cannot load on the New Architecture, camera or location access without the iOS permission text, and APIs removed from React Native core, and the ones it has announced it will remove (ImageBackground, SafeAreaView).

Improvement plan

Decide what to fix first

nativekeel improve orders existing security, crash, performance, store and dependency findings with reasons, conditions and verification. Exposed credentials get containment steps; unmeasured benefits and untested areas stay explicit.

Teams

Ratings, and every app at once

Each report rates Security, Store, Stability, Upgrade, Performance and Accessibility from A to E, the way SonarQube rates code. npx nativekeel fleet puts all your apps (client projects or a monorepo) in one table, worst first, with the store deadlines each one faces. Gate CI with --fail-on, keep one comment per pull request up to date, or send the findings to SonarQube. For teams →

Accessibility

Screen readers and large text

Icon-only buttons that VoiceOver and TalkBack announce as just "button", buttons too small to hit reliably, text with too little contrast, text fields with no label, text scaling turned off for the whole app, and Text.defaultProps settings that React 19 silently ignores. 282 of 871 open-source apps have at least one unlabeled icon button.

Performance

Performance review

Measure what your release bundle is made of with npx nativekeel bundle, from the source map your release build already wrote: each package's share and packages bundled twice. Timers and listeners started in an effect that nothing can stop, effects that refetch on every render, nested list patterns, large JSON (translations, Lottie) in the JavaScript bundle, animation settings, source logging, root imports and referenced large images. Confirm release inclusion and runtime impact before changing them; no speed or size saving is inferred from a source pattern.

Cleanup

Packages, files and images you may not need

Packages installed but never imported, source files nothing imports (it follows every import from the app's entry, aliases included, and stays quiet when it cannot resolve one), images no code or config references, backup copies such as Screen copy.tsx and leftover debugger statements. Listed for review, not automatic removal. Every package you can drop is one you never upgrade.

Experience

Known traps

Things that broke real upgrades, like an AppDelegate missing the one line React Native 0.77 requires, which crashes release builds with the New Architecture. The list grows with every upgrade we do.

From report to fixed

Everything you need to do the upgrade yourself, step by step.

Scan

Run npx nativekeel in your app folder. Share the HTML report with your team or client.

Upgrade readiness

nativekeel upgrade answers the one question before you start: what breaks in your own code and dependencies on the newest React Native / Expo, with file and line, and a clear go / no-go. Exit 1 when blockers remain, so CI can gate the upgrade pull request.

Plan

nativekeel plan orders the work: stop leaks, replace blockers, switch architecture, then upgrade React Native in reviewable hops.

Verify

After each step, nativekeel verify shows what got fixed and what is new compared with your last commit, so nothing slips in unnoticed.

Who builds it

NativeKeel is built and maintained by one engineer who ships React Native apps in production and checks every rule against real apps before it goes out.

AAAlican Akyol

Alican Akyol

Staff / lead engineer · mobile, frontend and backend

I have spent 14+ years shipping production systems end to end: mobile apps in React Native, iOS and Android, web frontends in React and Next.js, and the Node.js backends and API integrations behind them. I have built them for teams in banking, insurance, travel and research, including Fibabank, Anadolu Sigorta, Edenred, Turna.com, Setur and TÜBİTAK.

I also build and run my own React Native app in production, so I deal with store deadlines and native upgrades as an owner, not only as a contractor. My background in security engineering and malware analysis is why NativeKeel looks for leaked keys first.

14+ years in productionMobile · Frontend · BackendReact Native · React · Node.jsSecurity engineering

Expert help

The tool is free and stays free. If your team would rather hand the work over, the engineer who writes NativeKeel's checks takes on a few projects at a time.

Upgrade

Your app on the latest React Native or Expo

New Architecture migration, blocking libraries replaced, store requirements met, and the security and accessibility findings from the report fixed. Delivered as a pull request with test builds.

After the upgrade

Keep shipping without surprises

Monthly dependency and SDK updates, new Apple and Google requirements handled before their deadlines, build breakages fixed.

How it starts

Send the report

Run npx nativekeel --html report.html and email it. Within two business days you get a written, fixed quote with scope and delivery date.

You merge, not us

Work happens on a separate branch. Nothing is pushed to your main branch or released to your users without you.

Minimum access

One repository, removed when the work ends. Never your store passwords, signing keys or production secrets. Your NDA, if you have one.

Disclosed tools, 30-day warranty

AI assistants only under no-training terms, or none if your policy says so. Anything we changed that breaks within 30 days is fixed at no cost.

Ask about your app

FAQ

Can it tell me whether my app can be hacked?

It finds the common, detectable ways mobile apps get breached: open database rules, disabled certificate checks, keys and passwords in the app or its logs, unsafe WebViews, vulnerable dependencies. Findings are grouped by OWASP MASVS, the standard mobile security reviews use. What it cannot do is attack your running app and backend to prove nothing else is there; that is a penetration test, done with your permission. No matching findings is not proof of security; runtime and deployed backend checks remain separate.

Does my code leave my machine?

No. The scan runs locally. The only network requests are package-name lookups on npm and React Native Directory, and one request to npm's advisory endpoint with the names and exact versions of your dependencies (the same one npm audit makes). --offline makes none. Secret values are masked in every report.

Does it work with Expo and monorepos?

Yes. It reads Expo SDK versions and app.json, supports managed apps without native folders, and finds packages hoisted to a parent node_modules.

Is it really free? What is the catch?

The tool and the plan are free and open source under MIT, with no account and no paid tier. The project is funded by upgrades we do for teams that prefer to hand the work over; the report is the same either way.

Can I check what the tool does before running it on our code?

Yes. It has no dependencies and no install scripts, the source is short and public, and releases are published with npm provenance so you can verify the package matches the source (npm audit signatures). Run it with --offline to forbid all network access.

What if the report is wrong?

Version and maintenance data comes from npm and React Native Directory and can lag. Write to us and we will fix the rule. A missed upgrade blocker is a bug to us.