What's new
Every release, in plain words. Most changes come from two places: real upgrades we do, and scanning 850+ open-source React Native and Expo apps, more every week, to find what the tool gets wrong. Run npx nativekeel to always get the latest. Full notes on GitHub.
0.1.134
8 November 2026
More accurate Android playback findings and clearer scan coverage.
- StabilityTrack Player on Android. A Kotlin helper named
launchcan returnUnit, so a patched module using that helper no longer gets reported as returning a coroutine job. The scan now detects a separate crash path when Track Player'sMusicServicereadsreactNativeHostand the app only providesreactHost. - ReportsScan limits are explicit. The Stability grade describes static findings. Reports state when Firebase access rules could not be checked.
0.1.132
1 November 2026
A correction to last release's advice, and a check for the trap it could lead to.
- NativeTurning off expo-camera's barcode scanner also turns off CameraView scanning.
expo.camera.barcode-scanner-enabled=false(or the plugin optionbarcodeScannerEnabled: false) leaves ML Kit's barcode classes out of the Android build. The camera view then never attaches its barcode analyzer:onBarcodeScannednever fires, nothing crashes, andlaunchScannerrejects. NativeKeel now reports it when the setting is off and the app's code scans barcodes, with the file and line. None of the open-source apps that turn it off scan barcodes, so this is a guard, not a common bug. - StoreThe Android 16 note now leads with
tools:remove. For the portrait lock of Google's scanner activity, removing the attribute in AndroidManifest.xml is safe whether or not the app scans; turning the scanner off is only for apps that do no scanning with expo-camera at all. Both corrections suggested by a reader on r/reactnative.
0.1.131
31 October 2026
The orientation lock that expo-camera adds to your Android manifest.
- Storeexpo-camera's scanner activity is locked to portrait. Since expo-camera 16.1 (Expo SDK 53), the Android build includes Google's code scanner, and since 58 the document scanner too. Both declare an activity with
screenOrientation="portrait", so the merged manifest has an orientation lock even when your own activities have none and the app never opens the scanner. Android 16 ignores it on tablets and foldables, and Play Console's warning about orientation restrictions can point at it after you have removed your own locks. NativeKeel now lists it in the Android 16 note, with both ways out:expo.camera.barcode-scanner-enabled=false(anddocument-scanner-enabled) if you do not scan, ortools:remove="android:screenOrientation"on the activity if you do. In the open-source corpus the note now names it for 69 apps; for 11 of them it was the only lock, so there was no note before. Suggested by a reader on r/reactnative.
0.1.130
24 October 2026
Managed Expo apps: a stale target SDK pin no longer goes unnoticed.
- StoreTarget SDK pinned in expo-build-properties. A managed Expo app has no
android/folder, so the target SDK used to go unchecked. IftargetSdkVersionis pinned in the expo-build-properties plugin options, NativeKeel now reads it and applies the Google Play rule: a pin below 36 keeps the app below the level updates need after 1 November, even after an Expo SDK upgrade. The plan says where to change it. 15 of the managed Expo apps in the open-source corpus pin a value below 36. Suggested by a reader of the Google Play article.
0.1.129
24 October 2026
Deep links that launch the app, after the move to UIScene.
- StoreCold-start deep links lost after the move to UIScene. With the scene life cycle, a link that starts the app arrives only in the scene's connection options;
scene(_:openURLContexts:)andscene(_:continue:)see it only while the app is running. A SceneDelegate that forwards those two callbacks but starts React Native without the connection options passes a quick test and still opens on the first screen when a link launches the app. NativeKeel now reports it, and stays quiet when the options are passed (as in the React Native 0.88 template), converted to launch options, or read directly. Suggested by a reader of the Xcode 27 article.
0.1.128
24 October 2026
31 libraries checked, 30 listed: the dependency check now covers the libraries that matter most.
- UpgradeA wider list of libraries that still call removed APIs. 1,442 libraries used in the open-source corpus were scanned, and every hit was confirmed with the tool's own rules on the published code, with the exact release range it applies to: react-native-calendars (from 1.1275.0), react-native-elements, react-native-snap-carousel, react-navigation-stack, react-native-flash-message, react-native-ui-lib, react-native-svg-charts and 20 more. Libraries that carry their own copy of the API (Tamagui, Unistyles) are not reported.
- AccuracyCrash or layout. A dependency that calls
InteractionManageror aStatusBarsetter blocks the upgrade (it crashes when that code runs). One that usesStyleSheet.absoluteFillObjectis listed for review with the component affected (for example react-native-calendars' Timeline), because only those components lose their layout. A hook library such as@react-native-community/hooksis reported only where your code callsuseInteractionManager().
0.1.127
24 October 2026
Your code can be clean and the upgrade still break, because a library you depend on calls something React Native removed.
- UpgradeLibraries that still call removed APIs.
npx nativekeel upgradenow reads your installed dependencies forInteractionManager(removed in 0.87: a crash), theStatusBarsetters (0.87: a crash) andStyleSheet.absoluteFillObject(0.85: layouts break silently), and reports each library as a blocker of its own. Withoutnode_modulesit uses releases checked by hand: react-native-modal, react-native-draggable-flatlist 4.0.3, moti, React Native Elements, UI Kitten and NativeBase 3. On 1,162 open-source projects this changes the verdict for 24 apps whose own code was clean. A library's own copy of an API (a web shim) and calls guarded by a check are not counted. - HelpWhen you would rather hand it over. The upgrade verdict, the fix pages and the HTML report (unbranded, and only with a store deadline) say how to ask for a fixed quote. Reports made with
--brandnever carry it.
0.1.126
23 October 2026
Expo SDK 58 upgrades, covered more completely.
- UpgradeExpo Router SDK 58 changes in your code.
npx nativekeel upgradenow reportsinitialRouteName(removed, inunstable_settingsand on layout navigators),beforeRemovelisteners that stop firing,freezeOnBlurthat has no effect, and the removedredirect/initialParamsscreen props, each with file and line, from Expo's official migration guide. They apply only to apps that use Expo Router: plain React Navigation keeps them. Of 401 open-source apps on Expo Router below SDK 58, 78 setinitialRouteName. None of these show an error after the upgrade, so they are listed as behaviour changes to review. - GuidesExpo Router SDK 58: initialRouteName, freezeOnBlur and beforeRemove and expo-file-system File.write() is async in SDK 58: it still compiles without
await, but reads can race the write andtry/catchno longer sees write errors. Checked against the SDK 58 notes, the migration guide and the package's types; linked from the findings.
0.1.125
23 October 2026
A guide for the second most common upgrade blocker we measured.
- GuidesStatusBar backgroundColor and translucent removed in React Native 0.87. The props are silently ignored, but the setter calls (
StatusBar.setBackgroundColor) now throw. Why they went (Android 15 edge-to-edge) and how to colour behind the status bar with safe-area insets. 140 of 947 open-source apps below 0.87 use them. - UpgradeFindings link their guides. The
StatusBarandInteractionManageritems ofnpx nativekeel upgradelink to the page with the fix. A long explanation is shortened without cutting the link at its end. - Listedawesome-mcp-servers. NativeKeel is now in the largest list of MCP servers.
0.1.124
23 October 2026
See it before you run it.
- SiteThe upgrade check in action. The README and the homepage show a short recording of
npx nativekeel upgradeon a sample app: its real output, regenerated from the tool on every release, never typed by hand. It respects reduced-motion settings. - SiteWhere NativeKeel is listed. React Native Directory, the official MCP Registry, Glama and GitHub Marketplace.
- CLIColour follows the standards.
NO_COLORand--no-colorturn colour off in every command,FORCE_COLORturns it on where there is no terminal (CI logs). - FixEnd of support with the verdict.
upgradeshowed "React Native 0.84 is no longer supported" under "What this cannot confirm"; it is a known fact, now shown next to the verdict.
0.1.123
23 October 2026
Two new fix pages, linked from the findings that detect them.
- GuidesCVE-2025-11953 (Metro4Shell) in React Native. Which
@react-native-community/cliversions are affected (the official record), how to check a transitive copy, the override for each package manager, and the--host 127.0.0.1workaround. - GuidesStyleSheet.absoluteFillObject removed in React Native 0.85. In JavaScript nothing fails: overlays silently lose their layout. The one-line fix, checked against the React Native 0.85 source.
0.1.122
22 October 2026
AI agents pick the right NativeKeel tool more often.
- MCPClearer tool routing.
scan_project,security_audit,improve_appandupgrade_plannow say when to use them and which tool to use instead (a general health check, a security review, what to fix first, or the upgrade steps afterupgrade_readiness), after Glama's tool-quality review flagged the overlap.
0.1.121
22 October 2026
Supply-chain attacks land deep in the dependency tree, where package.json never names them. NativeKeel now looks there.
- SecurityKnown malware anywhere in the lockfile. Every package your lockfile resolves (npm, pnpm, yarn v1/berry, bun; often 1,000–4,000 of them, against 50–150 in package.json) is checked against GitHub's malware advisories, such as the October 2026 Shai-Hulud worm in
tensorlake@0.5.144that steals credentials on install. A hit is critical, cannot be ignored from.nativekeel.json, fails the CI gate, and stopsplan,improveand AI agents with a "do not install this project" warning. Only package names and versions are sent to npm, asnpm auditdoes. - AccuracyAliases are matched by what they install. An npm alias such as
legacy-swc-helpers → @swc/helpersis checked as@swc/helpers; a squatted package that only shares the local name is not reported. Ordinary advisories on packages the app does not name are left out: on 1,080 open-source apps, 83% had a critical one, almost all in build tooling, the noise that makesnpm auditignored.
0.1.120
21 October 2026
The upgrade catalog now reaches back a version: apps a few releases behind get real breaking-change content, not just a "multi-version jump" note.
- AccuracyReact Native 0.85 breaking changes.
StyleSheet.absoluteFillObjectwas removed in 0.85 (useStyleSheet.absoluteFill) and the Jest preset moved to@react-native/jest-preset.npx nativekeel upgradenow reports both for any app upgrading from 0.84 or below — 146 and 133 of 1,162 open-source React Native projects use them. (0.82–0.84 and 0.86 were checked against the release notes; 0.83 and 0.86 have no user-facing breaking changes.)
0.1.119
21 October 2026
Upgrade readiness you can trust: the breaking-change catalog audited against the official release notes.
- AccuracyMore React Native 0.87 breaking changes caught. Three cases the catalog was missing, so an upgrade now reports them instead of a false all-clear: deep imports from
react-native/src/private/(removed), and theDrawerLayoutAndroidand@react-native/assets-registrydeprecations. - TrustReact Native 0.88 confirmed non-breaking. Checked against the official 0.88 release notes: it has no user-facing breaking changes, so
npx nativekeel upgradereporting a clean 0.87 → 0.88 is correct, not a blind spot.
0.1.118
21 October 2026
A critical, actively exploited React Native vulnerability, found even when it hides in your lockfile.
- SecurityMetro development-server RCE (CVE-2025-11953). The Metro dev server's
/open-urlendpoint in@react-native-community/cli/cli-server-apiruns OS commands from a request (CVSS 9.8, in CISA's Known Exploited Vulnerabilities list): whilereact-native startruns, a web page a developer opens can take over their machine. NativeKeel reads the exact version resolved in your lockfile andnode_modules— so it catches it even when the cli is only a transitive dependency of React Native — and flags versions below the fixes (18.0.1, 19.1.2, 20.0.0). Found in 8 of 1,162 open-source React Native projects, two of them crypto wallets.
0.1.117
21 October 2026
The question every team asks before an upgrade, answered directly: npx nativekeel upgrade.
- NewUpgrade readiness.
npx nativekeel upgradegives a go/no-go for moving to the newest React Native / Expo: what breaks in your code and dependencies, with file and line, as blockers; behavior and tooling changes to review; and a clear verdict — READY, NOT READY (with the blockers), a multi-version jump (upgrade one step at a time), or already current. It exits 1 when blockers remain, so a CI job can gate the upgrade pull request. Also the MCP toolupgrade_readinessfor AI agents. - TrustHonest about multi-version jumps. An app several versions behind is never shown a clean "ready": the verdict says the catalog covers the newest step and the earlier steps have their own breaking changes, and points to
planfor the staged path. - FixFewer false alarms in the expo-file-system change.
File.write()becoming async is now flagged only on a realnew File(...)instance, not on any.write()in a file that happens to import expo-file-system (a database transaction was being flagged).
0.1.116
21 October 2026
A reliability release from a third production review, with no new checks: outputs that crashed, a comparison that missed regressions, and labels that claimed more than the scan knew.
- FixSARIF export no longer stops. A finding with several locations made
--sariffail (on 53 of 143 open-source apps we re-ran). Related locations now go through the same resolver as the main one. A new test passes every location shape through text, JSON, HTML, Markdown, SARIF and SonarQube output and checks that no path is missing or broken. - FixPaths with parentheses. Expo Router folders like
app/(tabs)/index.tsxare kept whole, and a sentence's opening bracket no longer becomes part of a file name ((index.js). - TeamsPull request gate sees regressions, not only new ids. A finding whose severity went up, or the same problem appearing in a new file, now counts as new and can fail the gate. The PR comment lists them under "Worse" and "In new files".
- AccuracyUnsure is not dead. When a project loads files by a computed path (
require.context,import(variable)), no file is labelled as code nothing imports; folders given torequire.contextcount as used. Security findings in unreached code keep their severity, and the label says "no import reaches", not "never runs". - AccuracyFewer files wrongly called unused. An import that names its extension (
./CheckoutScreen.js) now reaches the file; files run by a package.json script, Node scripts run by hand, web service workers, Flow library definitions, files inside another project in the repository (its ownpackage.json) and files read by name (readFileSync('sso.js')) count as used; code inside a string or in a build script no longer makes the whole check give up. - AccuracyA guard is not a leak. Code that reads
EXPO_PUBLIC_SUPABASE_SERVICE_ROLE_KEYonly to stop the app when it is set is no longer reported as shipping the key. - AccuracyLog silencing per method. A run-time no-op for
console.logno longer hidesconsole.infoorconsole.debugcalls, and a no-op inside a development-only branch does not count for release builds.
0.1.115
20 October 2026
From a second production review: "the biggest gain is not more findings, but tying them to the right place, showing how strong the evidence is, and turning them into priorities".
- FixSonarQube export no longer stops. Findings whose evidence is written as
file:linemade--sonarfail with "The path argument must be of type string". Every exporter now reads locations through one resolver, so issues also land on the real file and line written in a finding instead ofpackage.json:1. When most issues point outsidesonar.sources(fromsonar-project.properties), the export says so instead of letting SonarQube drop them silently. - ReportsHow strong the evidence is. Each finding says what it rests on, apart from its severity: a configuration file, source code (whether it runs was not verified), code the app never imports, the built app, or package versions. The HTML report groups findings by what to do with them: confirmed in configuration, found in source code, upgrade and maintenance, performance signals to measure, cleanup, notes.
- TeamsExceptions that expire. An accepted finding in
.nativekeel.jsoncan carry"until": "YYYY-MM-DD"; after that date it is shown again with a note to review it. - ReportsComparing scans from different versions. Results record the NativeKeel version, and
comparesays when two scans come from different versions, since part of the change can come from the checks rather than the app. - AccuracyOld is not abandoned. A package with no release for two years is no longer described as "no fixes will come": the report says to check its repository, and native packages that are only old drop from high to medium. Packages React Native Directory marks unmaintained keep the stronger wording.
- AccessibilityDecorations and inspectors. A Text holding only a symbol (✓, •, →) is not checked for text contrast, and network inspectors and similar developer tools are left out.
- AccuracyHow accurate is NativeKeel? A new page with the measurements: planted problems found, published vulnerabilities found, false alarms reviewed by hand per check, and known blind spots.
0.1.114
20 October 2026
- SecuritySupabase migrations: 28 of 45 databases analysed, up from 8. The policy checks stopped at any statement that might change a policy out of sight, and most real migrations have some: pg_dump's
SET search_path,select cron.schedule(…),alter table … add column, andDO $$ … IF NOT EXISTS … CREATE POLICY … $$blocks. Those are now understood (policies created inside such a block are read like any other). Renames, dynamic SQL, blocks that drop or alter policies, and SELECTs that call a function which changes them still stop the check for that database. In open-source apps this found two tables of people readable too widely: every user's email and date of birth to any signed-in user, and every user's phone number to anyone without an account.
0.1.113
20 October 2026
- SecurityScript injection in GitHub Actions. An issue or comment body, a pull request title or a branch name written into a
run:or github-script script with${{ }}, in a workflow started by issues, comments,pull_request_targetorworkflow_run(which have the repository's secrets and a write token). Plainpull_requestis left out: a fork already runs its own code there without secrets. Values passed throughenv:, used inif:or in an action'swith:, and jobs limited to a named user, a bot or the repository's own branches, are not reported. Checked on 12 public React Native workflows that use issue titles: all of them pass the value safely, and none is reported.
0.1.112
20 October 2026
From the same production review: "useful, but not something that should stop a release on every high finding".
- TeamsChoose which checks can fail the build.
"gate": ["secret:*", "ci-*", "android-16kb-libs"]in.nativekeel.json: only matching findings set the exit code and fail the pull request quality gate; everything else is still reported. Start with the checks you have seen to be right in your code. Planted malware always fails. - AccuracyDead code is labelled. A crash, performance, accessibility or code-security finding whose files the app never imports (followed from its entry point, only when every import resolves) is lowered two levels and marked "in code the app never imports": it cannot happen in the app as it is. Secret, store and dependency findings keep their level.
0.1.111
20 October 2026
Fewer false alarms, from a team that ran NativeKeel on a production app and checked every finding against its code.
- AccuracyAppDelegate window. An AppDelegate that subclasses
RCTAppDelegate(or Expo's app delegate) inherits itswindowproperty, so libraries that read it do not crash; the UIScene window warning no longer appears for it. - AccuracyFolly flags.
-DFOLLY_CFG_NO_COROUTINESset from the Podfile or in an.xcconfig(including the ones CocoaPods generates) counts, not only the Xcode project. - AccuracyRelease logging. A project's own Babel plugin that rewrites console calls, and console methods replaced with a no-op at run time (
console.log = () => {}in app code), count as removing logs from release builds. A wrapper that still writes the message does not count, and neither does a test setup file. - AccuracyServer-only advisories. moment's
moment.locale()path traversal advisories (GHSA-4p3w-j4w9-5jqw, GHSA-8hfj-j24r-96c4) say they affect server-side use only; they are now counted as Node.js only, so moment 2.29.3 reports its ReDoS as the vulnerability that applies. - ReportsWhich build the 16 KB check measured. The finding says whether it was a debug or release build, its date, and whether it is older than the last commit, with a note to build a current release before relying on it.
- AccessibilityDeveloper screens left out. Debug menus, dev tools and Storybook files are not checked: users never see them.
0.1.110
20 October 2026
- SecurityReads the database rules allow too widely. Firestore rules that let any signed-in user read a collection of people or private records (
users,profiles,messages,orders,payments…) with onlyrequest.auth != null, and Storage rules that do the same for every file in the bucket. Supabase: a table of people (users, profiles, patients, customers…) with columns such as email, phone or address and a SELECT policyusing (true)for anon or authenticated users. A hospital's or shop's phone is public on purpose, so only tables of people count. - SecurityPublic storage buckets with private names. A Supabase bucket such as
receipts,documentsorkyccreated withpublic = true: every file can be downloaded by URL without signing in. Found in an open-source expense app's receipts bucket.
0.1.109
20 October 2026
- SecurityCI workflows that run a fork's code with your secrets. A GitHub Actions workflow started by
pull_request_targethas the repository's secrets and a token that can write to it, for pull requests from any fork. If it checks out the pull request and then runs anything (npm ciruns the package's own scripts), the fork's author gets your EXPO_TOKEN, App Store Connect or Play credentials. Jellyfin's iOS app was exposed exactly this way (GHSA-7qhm-2m45-7fmh); NativeKeel reports its workflow before the fix and nothing after. Jobs limited to the repository's own branches or behind an approval environment, directly or throughneeds:, are left alone. Workflows are read from the repository root, also when the app is a folder of a monorepo. - ResearchWhat did not make it. Following tokens across files added one finding in 1,014 open-source apps, a false alarm: real apps log and send tokens under names the existing checks already recognize. WebViews that open an address from navigation parameters were never reachable from outside in the cases found. Neither was shipped.
0.1.108
20 October 2026
- SecurityURLs trusted after a text comparison.
url.startsWith('https://site.com')also acceptshttps://site.com.attacker.dev,url.includes('site.com')any address that contains it,host.endsWith('site.com')attackersite.com. Reported only where the check decides trust: a WebView navigation allowlist, a message origin check, or code nearby that sends credentials or acts on a deep link. Found in 3 open-source apps, among them a WebView that decides a payment succeeded fromurl.includes('payhere.lk'). - SecurityPrivileges the app grants itself.
isPremium: true,plan: 'pro', a role or credits written to Firestore, the Realtime Database or Supabase by the app: unless the rules stop users from changing that field, anyone can make the same write from a script. Fields the repository's Firestore rules or SQL mention are taken as protected; admin screens are left out. - SecurityLogin token sent to other sites. A global axios interceptor that adds the Authorization header to every request while the same axios also calls another site.
- CleanupDead code and leftovers. Source files nothing imports (every import is followed from the app's entry, tsconfig paths, babel module-resolver and root-import aliases included; files used only by tests, scripts or server functions count as used, and the check stays quiet if an import looks like an alias it cannot read), images no code or config references, backup copies (
Screen copy.tsx,App (2).tsx,.bak,.orig) anddebuggerstatements. Cleanup findings do not change the A–E ratings. On 245 reported images sampled from open-source apps, none was in use.
0.1.107
20 October 2026
Tested against vulnerabilities other people found: 10 published cases (GitHub security advisories of React Native apps, and commits that removed a leaked key, scanned just before the fix). Found: 5 before this release, 7 after.
- SecuritySentry auth tokens.
sntrys_andsntryu_tokens can read and change your Sentry organization; Sentry's own Expo plugin built them into apps in 5.16–5.19 (GHSA-68c2-4mpx-qh95). Found committed in 3 open-source apps. - SecuritySecrets in an Expo
app.jsonship in the app. Expo embeds the app config in every build (Constants.expoConfig), plugin options andextraincluded; onlyios.config,android.config, hooks and update-signing fields are left out. A key there is now reported as inside the app (critical), not only as committed. - SecurityMore server secrets read by app code: AWS secret access keys, Cloudinary API secrets, Twilio auth tokens, email API keys (SendGrid, Resend, Mailgun, Postmark), and any
EXPO_PUBLIC_, react-native-config or react-native-dotenv variable named*_SECRET,*_CLIENT_SECRETor*_PRIVATE_KEY. SDK secrets made to live in the app (Singular, Adjust) are left out. Found in 11 open-source apps. - AccuracyBuild files are not the app. A key in
sentry.properties,gradle.propertiesor a Gradle file is reported as committed, not as shipped: the build reads those files, it does not package them.
0.1.106
19 October 2026
- SecurityKeys added at build time. An
EXPO_PUBLIC_value set in EAS, or a CI secret written into a.envon the build machine, is compiled into the app but never appears in the repository, so no source scan can see it. NativeKeel now opens the built app and scans the JavaScript bundle inside it: APKs and AABs underandroid/app/build/outputs,eas build --localresults, committed bundles, and any APK, AAB or IPA passed with--artifact(or the GitHub Action's newartifactinput, after your build step). Hermes bytecode stores its strings back to back, so a key does not start at a word boundary there; only key formats with a distinctive prefix are matched inside bytecode, after a first version matched CSS names such asmask-imageas OpenAI keys. A key already reported from the source is not reported again.
0.1.105
19 October 2026
We built a test app with 41 known problems and counted how many NativeKeel finds: 59% before this release, 76% after. Each new check was run on 1,000+ open-source apps and every new finding was reviewed by hand before release.
- PerformanceTimers and listeners that can never be stopped.
setInterval,Keyboard.addListener,AppState.addEventListener,navigation.addListenerand similar calls in an effect whose return value is thrown away and that returns no cleanup: every mount adds another one, and they keep running after the screen closes. Found in 10 open-source apps. - StabilityRequest loops. An effect with no dependency array that fetches and stores the result sends a new request after every response.
- SecurityCredentials in release logs. Session tokens, API keys and passwords passed to
console.login code that ships. Logs insideif (__DEV__), builds that strip console calls, push tokens, flags such as!!token, and server or tooling folders are left out. Found in 25 open-source apps. - SecurityMore of what was already checked: redux-persist keeping the auth slice in AsyncStorage, plain-HTTP API addresses kept in a constant (
const API_BASE = 'http://…'), Android activities exported with no intent filter and no permission, and Redux selectors written with TypeScript types. Private network names (.local, VPN ranges) and commented-out lines are no longer reported as plain-HTTP calls.
0.1.104
19 October 2026
- ReportsThe HTML report's low count adds up. Outdated packages are counted as low findings but sat in a closed table at the very end, after the notes, so a report could say "12 low" and show two. The table now comes right after the other low findings, open when it is short, and the low card says how many of them are outdated packages. Finding ids sit on their own line instead of breaking mid-word.
0.1.103
18 October 2026
More from the same developer's feedback on a real project.
- AccuracyFiles git ignores are not scanned for code findings. A local scratch folder, generated code or anything else in
.gitignoreno longer produces console, deprecated API, upcoming change, image, render loop, accessibility or security source findings: it is not in the repository or in CI. Secret checks still read ignored files, because an ignored.envcan be compiled into the app. - PerformanceMetro's
drop_consoleis recognized. Withtransformer.minifierConfig.compress.drop_console(orpure_funcslistingconsole.log) inmetro.config.js, the logging note no longer appears. - AccessibilityGesture Handler buttons are checked.
PressableandTouchable*imported from react-native-gesture-handler get the same label, role and touch-size checks as React Native's own.
0.1.102
18 October 2026
From the feedback of a developer who tried NativeKeel on a real project.
- TeamsFinding ids in the report. Every finding shows its id in brackets (terminal, Markdown and HTML), so accepting it in
.nativekeel.jsonno longer needs--json. - TeamsExclude folders.
"exclude": [{ "path": "tools/admin-web", "reason": "…" }]in.nativekeel.jsonleaves out findings whose files are all inside folders that are not part of the app. They stay listed as excluded, and malware warnings are never excluded. - Securitygit-crypt and transcrypt. Files encrypted on commit (
filter=git-cryptorfilter=cryptin.gitattributes) are no longer reported as committed keystores, keys or passwords: the repository only holds the encrypted file. A secret in them that the app bundles is still reported. - PerformanceDevelopment-only logging is not counted.
console.loginsideif (__DEV__), after__DEV__ &&, or behind aNODE_ENV !== 'production'check does not run in release builds and no longer counts toward the logging note.
0.1.101
18 October 2026
- UpgradeFewer false alarms on React Native 0.87. A React header imported without
React/is no longer reported when it sits in code that only compiles for the old architecture (#ifndef RCT_NEW_ARCH_ENABLED): React Native 0.82 and later always build the New Architecture, so that code never reaches the compiler. - ResearchReact Native 0.88 library readiness. We checked the 590 most downloaded React Native libraries with native code against the two 0.87 changes that break builds and apps: 18 break. For 6 of them we sent a fix, each tested in a React Native 0.87.1 app (fails before, builds after).
0.1.100
18 October 2026
- AI agentsClearer MCP tools. Every parameter of the eight MCP tools now says what it does and its default,
upgrade_plandescribes what the plan contains, and every tool carries the standard MCP annotations (read-only, non-destructive, idempotent, and whether it uses the network), which agents and registries use to decide when to call it.
0.1.99
18 October 2026
- SecurityBackend admin credentials inside the app. A key that bypasses your backend's own access rules lets anyone who unpacks the app read or change every user's data. NativeKeel now reports, when the app reads them through
EXPO_PUBLIC_, react-native-config or react-native-dotenv (which compile the value in): the Supabaseservice_rolekey, a Hasura admin secret, Firebase service account keys, database passwords, the Stripe secret key, Appwrite API keys, PocketBase superuser passwords and JWT signing secrets. Also: server-only SDKs (firebase-admin,pg,mongodb,stripe, …) imported by files that are certainly app code, and database connection strings with a password or Hasura admin secrets written in the code. Tuned on 1,040 open-source apps: names that are usually public (FIREBASE_DATABASE_URL), server services in the same repository and placeholder passwords are left out.
0.1.98
18 October 2026
- Fewer false alarmsReact header imports in your own app code are no longer reported. The React Native 0.87 header check also flagged
#import <RCTAppDelegate.h>in an app's own AppDelegate or bridging header. We compiled those forms in the app target of a 0.87.1 app: they still resolve there. Only libraries, which CocoaPods builds as separate targets, fail. Found while checking two open-source apps on 0.87.1 that build fine and were wrongly flagged.
0.1.97
18 October 2026
- New checkRender loops. State updates that run on every render freeze the screen and end in "Too many re-renders" or "Maximum update depth exceeded". NativeKeel now finds the three patterns behind them, with file and line: a handler called instead of passed (
onPress={setOpen(true)}), an effect with no dependency array that sets a new value, and an effect that changes the state it depends on. Guarded, constant and asynchronous updates are left alone.nativekeel explainrecognises both messages. Fix page.
0.1.96
18 October 2026
- ExpoReact Native that does not match the Expo SDK. An Expo SDK's native modules are built against one React Native minor; a different one is a common cause of build failures and launch crashes. NativeKeel now compares them (found in an app with Expo 58 and React Native 0.87, where the SDK expects 0.88), and says when the installed
expostill pins a release candidate. The informational line about React Native and the Expo SDK no longer claims they match.
0.1.95
18 October 2026
- Google PlayWhat changes at API 36 (Android 16). Google Play requires API 36 for updates since 31 August 2026, and the extension ends on 1 November. NativeKeel now reports an edge-to-edge opt-out (
windowOptOutEdgeToEdgeEnforcement) that Android 16 ignores, so screens slide under the system bars, and notes the orientation and aspect ratio locks that tablets and foldables ignore. Games are exempt; the temporary resizability opt-out is mentioned. Target API level page updated with the API 36 changes.
0.1.94
17 October 2026
- TeamsTeam panel, closed beta. With
--uploadand a team token, each scan (orfleetrun) sends a summary to your team's page: every app's grades, what changed since the scan before, a trend over the last scans, deadlines and finding titles. No source code and no finding details are sent, and--uploadnever works with--offline. The GitHub Action takes apanel-tokeninput, and the monthly organization workflow uploads when aNATIVEKEEL_TOKENsecret is set. Live demo · join the beta. What is stored: privacy.
0.1.93
17 October 2026
- SonarQubeNativeKeel findings inside SonarQube.
npx nativekeel --sonar nativekeel-sonar.jsonwrites SonarQube's generic issue format; the scanner reads it withsonar.externalIssuesReportPaths. Security findings arrive as vulnerabilities, store rules and crash risks as bugs, the rest as code smells, each on its file and line, in the same project and quality gate as the rest of your code. The GitHub Action has asonarinput. Tested end to end on SonarQube Community Build 26.10. How to set it up.
0.1.92
17 October 2026
- React Native 0.88React Native 0.88 and Expo SDK 58 are stable, and reports now say so. The Xcode 27 / UIScene finding names the official 0.88 path: the new SceneDelegate entry points in
RCTReactNativeFactory, forwarding links toRCTLinkingManager, one scene only. Updated fix page. - TeamsEvery app in a GitHub organization, monthly. A ready-made workflow (examples/fleet-workflow.yml) clones the organization's repositories on the GitHub runner, runs
fleet, compares with last month and writes the table to the run summary. Tested on GitHub with three public apps. - Deprecated
InputAccessoryViewis deprecated in 0.88 and warns once on import; the report points to react-native-keyboard-controller'sKeyboardStickyView.
0.1.91
17 October 2026
- FleetWhat changed since last month. Keep a run with
npx nativekeel fleet ~/clients --json > fleet-2026-10.json; next time,--base fleet-2026-10.jsonshows per app what changed ("Security D→B, critical 2→0"), which apps are new and which are gone, in the terminal, the HTML page and Markdown. Nothing is stored anywhere but the file you keep. - Compare
npx nativekeel compare before.json after.jsonnow includes the A–E rating of each area before and after.
0.1.90
16 October 2026
- TeamsQuality gate in pull requests. The GitHub Action's pull request comment now starts with "Quality gate: passed" or "failed" (failed when the change adds a critical or high finding), and shows the A–E ratings with what changed ("Security E (was B)").
- Teams
.nativekeel.json: the team's decisions in the repository. Set the gate level (failOn) and list findings the team has accepted, each with a reason. Ignored findings stay listed in every report;--fail-onstill wins; malware warnings cannot be ignored. The scan,fleet,verify, the GitHub Action and the MCP tools all follow it. - FleetApps outside the current folder are shown from the folder you gave, not as
../../paths; without--fail-on, each app's own.nativekeel.jsondecides.
0.1.89
16 October 2026
- NewRatings from A to E. Every report (terminal, HTML, Markdown, JSON) now rates six areas the way SonarQube rates code: Security, Store, Stability, Upgrade, Performance and Accessibility. A means nothing found in that area, E at least one critical finding. Ratings follow the baseline, so CI sees what is new.
- New
npx nativekeel fleet: every app at once. Point it at a folder of client projects or a monorepo and it scans each React Native and Expo app, then shows them in one table, worst first: versions, the six ratings, critical and high counts, and the store and end-of-support deadlines each app faces.--htmlsaves a page you can share (with--brand),--markdownand--jsonwork too, and--fail-onapplies across all apps.
0.1.88
16 October 2026
- New checkLibraries that stop the iOS build on React Native 0.87. React Native 0.87 serves its iOS headers from XCFrameworks, so a library that writes
#import "RCTBridge.h"instead of#import <React/RCTBridge.h>fails with "file not found". NativeKeel now reads the iOS code of your installed libraries and your own: before the upgrade it lists them as work for 0.87, after it as the reason the build fails. We compiled every React Native header both ways to know exactly which imports break; among the 248 most downloaded native libraries it finds 5, including react-native-date-picker, @react-native-menu/menu and react-native-bottom-tabs. Fix and workaround. - CrashOn React Native 0.87 and later, code that still uses
InteractionManageris reported as a crash with the file and line (it was only listed as upcoming work before). How to move to requestIdleCallback. - Explain
nativekeel explainrecognises any "'RCT….h' file not found" and the development-build InteractionManager message.
0.1.87
15 October 2026
- ReportHelp line only when there is a deadline. The terminal report used to end with a link to the help page on every scan with serious findings. Now it shows one line with the contact address, and only when a critical or high finding has an outside deadline: Play target SDK, 16 KB pages, Xcode 27 UIScene, unsupported React Native or Expo, or New Architecture off. CI, JSON, SARIF and MCP output are unchanged.
0.1.86
15 October 2026
- Fix guide"Failed to call into JavaScript module method RCTEventEmitter.receiveEvent()". A new page explains this React Native 0.77+ error (often blamed on SafeAreaProvider): the AppDelegate is missing
RCTAppDependencyProvider. It gives the line for Objective-C, Swift on 0.77–0.78 and Swift on 0.79+. The finding that detects it links to the page.
0.1.85
15 October 2026
- Fix guide"-[AppDelegate window]: unrecognized selector". A new page lists the libraries that crash this way after the move to UIScene, when each one crashes and its fix (pull requests sent to image-crop-picker, ui-lib, date-picker, contacts, snackbar and print today), plus a one-line workaround in your own AppDelegate. The crash finding links to it.
- ReportsThe terminal report and upgrade plan point to Expert help instead of the old pricing section, which no longer exists.
0.1.84
15 October 2026
- NewCheck a package.json in your browser. nativekeel.com/check runs the CLI's own analysis in the page on the package.json (and app.json) you paste: unsupported React Native and Expo versions, libraries without New Architecture support or no longer maintained, major updates, and the upgrade plan. Your file stays in the tab; the page asks npm, React Native Directory and unpkg about the package names, the same lookups the CLI makes. Known vulnerabilities and everything that needs your code (leaked keys, native files, store settings, accessibility) stay in
npx nativekeel.
0.1.83
15 October 2026
- CIA comment on every pull request. With
pr-comment: trueandpull-requests: write, the GitHub Action compares each pull request with its base commit and keeps one comment up to date: the findings this pull request adds or fixes, by severity, and the app's totals. It is edited on every push, not repeated, and no code runs. Pull requests from forks only get the job summary, because their token is read-only. - Fix
verifyno longer reports old signing material as new. The committed version was unpacked without git metadata, so committed keystores and signing passwords were missing on that side and showed up as new in every comparison (and in the MCP toolverify_upgrade). Files from the committed version now count as committed.
0.1.82
15 October 2026
- PerformanceCompare two builds.
npx nativekeel bundle new.map --base old.mapshows what changed between two release builds: packages added or removed, packages that grew or shrank by 1 KB or more, and packages now bundled twice. Tested on a real Expo app: oneimport _ from "lodash"line showed up as +107 KB. The MCP toolmeasure_bundletakes the samebase.
0.1.81
15 October 2026
- PerformanceMeasured bytes in the findings. When a release source map is present, the lodash and moment finding says how much of the measured bundle each one really takes (moment's locale files separately), or that the package is not in the bundle at all, instead of only pointing at the import.
- AI agentsMCP tool
measure_bundle. Claude Code, Codex and other MCP clients can ask what the release bundle is made of: the app's share, each package's share, packages bundled twice and the largest JSON. The map must be inside the project folder the server may read.
0.1.80
15 October 2026
- PerformanceMeasure the release bundle.
npx nativekeel bundlereads the source map a release build already wrote (Android Gradle writes one underandroid/app/build/generated/sourcemaps/react/release/; Expo withnpx expo export --dump-sourcemap) and shows how much of the shipped code is your app and each package, measured rather than guessed. Hermes bytecode maps work too. The normal scan reports the composition when it finds a map, and packages bundled twice (two versions of the same library) with their measured size. Nothing is built or run; strings and bytecode metadata have no source and are left out.
0.1.79
15 October 2026
- AccuracyPush and invitation tokens are not auth tokens. The unencrypted-token check reads a storage key's constant value from the same file and the file's name, so a push-notification token behind
SYNCED_KEYinpushRegistration.tsis no longer reported; single-use invitation tokens are not either. Found by scanning a real production app. - AccuracyLarge JSON required inside a function. It is still in the bundle every user downloads, but it is evaluated only when that code runs; the finding now says so instead of implying it loads at start.
- CorpusThe weekly scan added 149 apps (1,040 in total); the newer checks were spot-checked on them by hand.
0.1.78
15 October 2026
- OTA updatesRuntime version kept by hand. expo-updates sends an update only to builds with the same runtime version. When it is a hand-written string or follows the app version, an update made after a native change can reach builds without that native code; Expo's documentation calls this a runtime version mismatch. NativeKeel now adds a note and points to the fingerprint policy. 59 of the 107 open-source apps using expo-updates manage it by hand.
- OTA updatesCodePush. The react-native-code-push finding now says that Visual Studio App Center was retired on 31 March 2025 and Microsoft archived both the client and its standalone CodePush server: without your own server, updates sent this way no longer reach users.
0.1.77
14 October 2026
- SecurityDatabases visible in the Files app. With iOS file sharing on (
UIFileSharingEnabled, in Info.plist or app.json), the app's Documents folder shows up in Finder and, withLSSupportsOpeningDocumentsInPlace, in the Files app. react-native-mmkv, expo-sqlite and Realm keep their data in Documents by default on iOS (checked in each library's source), so an unencrypted database can be copied out by anyone holding the unlocked phone. Encrypted stores and stores with a custom location are not reported.
0.1.76
14 October 2026
- SecurityBiometric unlock that only checks a yes/no. When an app asks for Face ID, Touch ID or a fingerprint and trusts the success result, but no secret or key is bound to biometrics anywhere (react-native-keychain access control, expo-secure-store
requireAuthentication, react-native-biometrics signatures, or the iOS/Android native equivalents), the prompt guards the screen, not the data. The finding states the prerequisite plainly: physical access to a jailbroken or rooted device with instrumentation (OWASP MASTG local authentication). Found in 41 of 871 open-source apps, wallets among them. - AccuracyThe README now describes unused packages as review candidates, as the report has since 0.1.68.
0.1.75
14 October 2026
- AccessibilityPlaceholder text is checked for contrast. People read the placeholder to know what to type, and WCAG treats it as text. A literal
placeholderTextColoris compared with the input's own background or, when it has none (inputs are transparent by default), the view behind it. 226 placeholders in 55 of 871 open-source apps fall below 4.5:1, often light grey on white.
0.1.74
14 October 2026
- PerformanceLarge JSON in the JavaScript bundle. JSON files over 300 KB imported or required from app code become modules in the bundle, so every user downloads them and the app loads them with everything else. Translations for every language get "load only the active language"; Lottie animations get "use a .lottie asset". Dynamic imports, tests, fixtures and stories do not count. Found in 19 of 871 open-source apps (up to 11 MB in one).
- AccessibilityA note (not a warning) when touchables have no
accessibilityRole: screen readers then do not say they can be pressed. It is missing in 94% of the open-source apps that use touchables, so it is listed without raising the severity.
0.1.73
14 October 2026
- NewText that is hard to read. Where a React Native
Texthas a literal color and the nearest background behind it is a literal opaque color (inline or in the file'sStyleSheet), pairs below WCAG 2.2 AA are reported with both colors and the ratio: 4.5:1 for normal text, 3:1 for large text. Themed, computed or translucent colors, opacity, images and custom components between the text and its background are left alone. Found in 180 of 871 open-source apps; samples checked by hand.
0.1.72
14 October 2026
- NewButtons too small to tap. React Native touchables whose tappable area is certainly under 44×44 points (an explicit width and height below 44 in an inline style or the file's
StyleSheet, or no style around a single small icon) and nohitSlop. Apple recommends 44×44 pt and Android 48×48 dp; the report says separately when a button is also under the WCAG 2.2 AA minimum of 24×24. Sizes it cannot read (computed, spread, flex) are left alone. Found in 209 of 871 open-source apps; samples checked by hand.
0.1.71
14 October 2026
- NewAccessibility checks. Icon-only buttons (React Native touchables with just an icon or image) that have no
accessibilityLabel: VoiceOver and TalkBack announce them as an unnamed "button". Text fields with no label or placeholder. Text scaling turned off for the whole app. On 871 open-source apps, 282 have at least one unlabeled icon button and 119 an unlabeled text field; samples were checked by hand. - Upgrade
Text.defaultPropsstops working on React 19. React Native 0.78 ships React 19, which applies defaultProps only to class components; React Native and Expo compile JSX with the automatic runtime, so app-wide fonts or font-scaling limits set this way silently stop applying. Apps on 0.78+ are told the setting has no effect; older apps are warned before the upgrade. Projects using NativeWind or the classic JSX runtime, wherecreateElementstill applies them, are not flagged. - Plan
nativekeel improvehas an accessibility group with VoiceOver/TalkBack and largest-text verification, and the upgrade plan a phase for it.
0.1.70
12 October 2026
- SecurityAI keys in the app bundle are treated as exposed credentials. In
nativekeel improvethey are marked for containment, suggest a provider spending limit until the key is revoked, and recovery never puts a provider key back into the app. - PlanCommitted signing passwords and keystores get signing-specific checks (who had access, Play upload key reset, release signing from protected storage) instead of provider access-log advice. React Native, Expo, New Architecture and native-project work has its own "upgrade" group with build-and-test verification, instead of dependency-replacement advice.
0.1.69
12 October 2026
- FixOne odd package.json entry no longer stops the scan. Since 0.1.64 a dependency name that is not a valid package name (a typo such as
"@types/", or a workspace alias such as"@global-ui") refused the whole scan. Those entries are now skipped with a warning, and they still never reach a path, a command or a registry request. Found in 3 of 871 open-source apps when rescanning them with 0.1.68. - PlanOn React Native before 0.76, the improvement plan now says how to switch on the New Architecture (after upgrading to 0.76–0.81) instead of pointing back at the finding. Other actions without their own steps point to
npx nativekeel plan.
0.1.68
12 October 2026
- PlanReview the whole app in order.
nativekeel improveand MCPimprove_appturn existing security, crash, performance, store and dependency findings into actions with applicability conditions, verification and recovery. Each action carries the same concrete steps as the upgrade plan. This adds a decision layer, not new vulnerability detectors. - SecurityExposed credentials need containment. Secret findings get provider revocation or rotation steps rather than a generic instruction to reproduce an exploit. Dedicated test keys, comments and platform signing identities have separate guidance. Recovery never restores a leaked credential.
- AccuracyReview dependencies before removing them. Optional and nested installed references are checked, and incomplete evidence suppresses unused candidates. Dynamic, native and generated consumers still need review. Upgrade advice is retained.
- PerformanceSource logging, list and import patterns no longer imply measured release cost or speed gains. Terminal output is plain text; saved plans use escaped Markdown. Narrow import experiments remain documented separately from the main CLI help.
0.1.67
11 October 2026
- FixThe Codex plugin can scan projects again. Since 0.1.64, a server started inside a plugin folder needed
NATIVEKEEL_MCP_ROOTS, but Codex does not let users set environment variables for a plugin's server, so every scan from the plugin was refused. Codex starts plugin servers in the plugin's own folder, which says nothing about the open project, so the boundary there is your home folder again. To limit it to one project, configure the server yourself in~/.codex/config.tomlwithNATIVEKEEL_MCP_ROOTS. The tools stay read-only, never run project code and never return source code. Claude Code is not affected: it starts the server in the project folder.
0.1.66
11 October 2026
Six native Android checks trace archive entry paths into file writes and incoming Intent fields into launches, WebViews, local SQL and file reads/writes. An explicit exported manifest entry and matching Java/Kotlin class are required for Intent findings; literal Gradle namespaces are supported. Reports state the attacker prerequisites, Android 14/16 protections and verification steps. Guarded or complex flows are unresolved, not marked safe.
270 tests pass. A read-only pass over 922 repositories produced no new matching findings; this is scope calibration, not a security certificate. No app or malicious sample was run. Coverage and limits →
0.1.65
11 October 2026
nativekeel securityand MCPsecurity_audit: a focused report of data exposure, account access and code execution risks.- Eight new checks: credentials in telemetry and URLs, WebView/network data evaluated as code, external input in SQLite query text, PKCE disabled, implicit OAuth tokens, and broad private FileProvider paths.
- New findings include source evidence, attacker prerequisites, a fix and local verification steps. SARIF points to the evidence. Reports show coverage limits; zero findings is not a passed security assessment.
0.1.64
11 October 2026
- SecuritySafer scans from AI agents. MCP checks project file reads against allowed roots, rejects unsafe dependency names, and keeps malware stop warnings in upgrade plans, error explanations and verification results. A project with suspected malware no longer gets a plan that starts by running tests. Removed instruction-like object keys are not echoed in diagnostic paths. These defenses reduce risk; text filtering cannot make an agent immune to prompt injection.
- SecurityMore access-control checks for mobile backends. Finds Firebase write rules that only require sign-in and supported Supabase migrations with unconditional SELECT and UPDATE/DELETE policies for anonymous or signed-in users. Reports source locations and prerequisites; does not claim the rules are deployed or that a live attack succeeded. Public reads, insert-only forms and restrictive policies are handled conservatively.
- ConfigurationPlugin servers need explicit project roots. Set
NATIVEKEEL_MCP_ROOTSin the MCP server environment when it starts inside a plugin directory. The home folder is no longer granted automatically. For monorepos, allow the workspace root if hoisted dependencies must be read.
0.1.63
11 October 2026
- AI agentsCodex plugin.
codex plugin marketplace add AlicanAkyol/nativekeel, thencodex plugin add nativekeel@nativekeel. It adds the MCP server, pinned to the release, and the same skill as the Claude Code plugin, so Codex checks the project before upgrades and library changes, explains errors and verifies the upgrade before you commit. Built on the open Agent Plugins format and installed with Codex CLI 0.162. - SecurityFolder boundary for servers started inside a plugin. Codex starts plugin servers in the plugin's own folder, which says nothing about the project you have open. There NativeKeel uses your home folder as the boundary, or only the folders in
NATIVEKEEL_MCP_ROOTSwhen you set it.
0.1.62
11 October 2026
- NewCheck an upgrade before you commit it.
npx nativekeel verifycompares the project as committed (HEAD, or--baseany branch, tag or commit) with your working tree: what got fixed, what is new, and how React Native, Expo and the dependencies moved. It exits with 1 when the change adds a critical or high finding, so it works as a pre-commit or CI check. AI agents get the same as theverify_upgradeMCP tool, and the Claude Code plugin tells Claude to run it after an upgrade. The committed version is unpacked withgit archiveinto a temporary folder outside the project and deleted afterwards; revisions that look like options or ranges are refused, and the repository's own git config cannot make it run anything.
0.1.61
11 October 2026
- NewExplain an error.
npx nativekeel explain "<error>"(or pipe a log into it), andexplain_errorfor AI agents over MCP: what a build, launch, crash or App Store / Google Play review error means and the fix. Add--path .to see where your project is affected, from the same checks as the scan. It covers 21 errors we reproduced or verified at the source, among them-[AppDelegate window]: unrecognized selectorwith the React Native 0.88 template,'RCTComponent.h' file not found,InteractionManagerremoved in 0.87, ITMS-91061, Xcode 27's UIScene requirement, the 16 KB page size warning and App Store 5.1.1(v). The error text is matched on your machine and never sent anywhere. - AI agentsThe Claude Code plugin installs NativeKeel from a lockfile with the package's integrity hash instead of downloading it on every start, and has an icon.
0.1.60
11 October 2026
- FixExpo SDKs are named with the React Native version they ship ("Expo SDK 58 (beta, React Native 0.88)"). In our test an AI agent read "SDK 58" next to the React Native 0.87 changes and told the user SDK 58 ships 0.87.
0.1.59
11 October 2026
- UpgradeWhat changes in the next version, in your code. Release notes list everything; NativeKeel now lists only the changes that touch your app, each with
file:lineand what to do, and includes the next version while it is still in beta. For React Native 0.87:InteractionManager, theStatusBarbackgroundColor/translucentprops,Modal animated, booleankeyboardShouldPersistTaps, deep imports that become type errors, bare#import <RCT…h>lines, Node.js 22.13+. For Expo SDK 58 (beta): R8 on by default in release builds,File.write()becoming async, libSQL removed from expo-sqlite, foreground notifications shown by default, the expo-router navigation rework,NODE_ENVset before.envloads, and more. Measured on 675 open-source apps: 578 are touched by at least one change, most often R8 (479 apps), theStatusBarprops (103) andInteractionManager(47). We added this after watching an AI agent find the SDK 58 changes on the web that NativeKeel did not know about.
0.1.58
11 October 2026
- AI agentsThe Claude Code plugin runs an exact NativeKeel version instead of whatever is latest on npm, and updates with each release. Its README lists what it runs, what it reads and the only data it sends (package names and versions, to npm, React Native Directory and unpkg; no source code, no telemetry).
0.1.57
11 October 2026
- AI agentsClaude Code plugin.
claude plugin marketplace add AlicanAkyol/nativekeel, thenclaude plugin install nativekeel@nativekeel. It adds the MCP server and a skill that tells Claude when to use it: before upgrading React Native or Expo, adding a native library, preparing a store release, or running a project you did not write. In our test Claude used it without being asked, took 7 turns instead of 16, and found a store-blocking issue it missed on its own. Details. - AI agentsOne-click install in Cursor and VS Code, and a one-line
AGENTS.mdrule for agents without MCP. - SecurityMCP server started in the filesystem root. Some clients start servers in
/, which made every folder readable to the scan. That folder no longer counts; name your projects withNATIVEKEEL_MCP_ROOTS.
0.1.56
11 October 2026
- SecurityMalware planted in a project, found before you run it. Fake job tests and sample projects sent to developers hide code that steals credentials and crypto wallets. They use three tricks: a VS Code task with
"runOn": "folderOpen"that runs when the folder is opened, code hidden after a long run of spaces at the end ofbabel.config.js(Babel loads it on every start and build), and JavaScript saved as a font file. While scanning 925 open-source React Native and Expo repositories we found four that still contain it, one with 69 stars and 17 forks, and in one the commit titled "Remove injected malware" is the one that adds it. NativeKeel now reports these as critical and says not to install, start or open the project until it is cleaned. It reads these files and never runs anything from the project, so it is safe to run first on a repository you do not trust. With 0 false alarms on the other 921 repositories. Over MCP, the result carries a warning telling the AI agent not to run the project. - SecurityVisible auto-run tasks. A VS Code task that runs on folder open but does nothing suspicious is a medium note, so whoever clones the repository knows what runs.
0.1.55
10 October 2026
- AI agentsListed in the official MCP Registry as
io.github.AlicanAkyol/nativekeel, so MCP clients and directories that read the registry can find and install it. Every release updates the listing from GitHub Actions: ownership is proven with the workflow's OIDC token (no stored secret), and the publisher tool is pinned and checksum-verified.
0.1.54
10 October 2026
- SecurityKeychain items readable while the device is locked. The "Always" accessibility levels (
ACCESSIBLE.ALWAYSin react-native-keychain,SecureStore.ALWAYSin expo-secure-store,kSecAttrAccessibleAlwaysand theirTHIS_DEVICE_ONLYvariants) let an item be read whether or not the device is locked, so the passcode no longer protects it. Apple deprecated them in iOS 12. Reported as medium with the replacement (AFTER_FIRST_UNLOCKfor background access,WHEN_UNLOCKEDotherwise). Found in 3 of 880+ open-source apps: two Lightning wallets and a clinic records app. (OWASP MASVS-STORAGE)
0.1.53
10 October 2026
- NewNativeKeel for AI coding agents (MCP).
npx nativekeel mcplets Claude Code, Codex, Cursor and other MCP clients scan a project, get the upgrade plan and check a library against your React Native version, instead of guessing. Read-only, scans only the folders you allow, never returns source code, and removes text in the repository that tries to give the agent instructions. Set it up. - SecurityA scanned repository can no longer run a command through git. NativeKeel runs
git ls-filesto know which files are committed, and a repository's own.git/configcan make that run a program (core.fsmonitor; checked with git 2.50.1). That matters when you scan a project you did not create, such as a zip with its.gitfolder. Every option that runs a program is now switched off for the scan, and a test plants one and fails if it runs. - DocsSECURITY.md now explains how untrusted projects are handled, how the MCP server is isolated, and for each security check what it can and cannot detect.
0.1.52
10 October 2026
- App StoreXcode 27: the UIScene life cycle. Built with the iOS 27 SDK, an app that has not adopted the scene life cycle stops at launch ("UIScene life cycle is required for apps built with this SDK"), and App Store Connect requires that SDK from April 2027. NativeKeel now says whether your app has adopted it and what to do: React Native 0.88 is the first template with it; Expo SDK 57 opts in with
ios.enableSceneSupport; SDK 58 has it by default. 767 of 833 iOS apps in our scan have not adopted it yet. What to change. - CrashWhat breaks after the move. Deep links and universal links that are still handled only in AppDelegate stop arriving. Libraries that read the window from the app delegate crash with "-[AppDelegate window]: unrecognized selector" on the React Native 0.88 template. We reproduced this on that template and sent fixes to react-native-blob-util and react-native-google-mobile-ads. NativeKeel lists the installed packages that do it and the one-line workaround.
- FixStore review checks were not running. Since 0.1.42, a refactor left the account deletion (5.1.1(v)), Sign in with Apple (4.8) and iOS SDK privacy manifest (ITMS-91061) checks out of the report. They run again, and a new test fails if any check stops being called.
0.1.51
9 October 2026
- SecurityRecovery phrases and private keys copied to the clipboard. Keyboards with clipboard history and cloud clipboard sync keep a copy, every app the user pastes into receives it, and on Android 9 and older any background app can read it. Reported as medium when a seed phrase, mnemonic, private key or secret key goes to the clipboard and is not cleared again (a timer that clears it after a minute counts as cleared). Found in 8 of 869 open-source apps, almost all crypto wallets. (OWASP MASVS-STORAGE)
- Play Storeexpo-sqlite's sqlite-vec option breaks 16 KB alignment. With
withSQLiteVecExtension(oruseLibSQLon SDK 57), expo-sqlite adds a prebuilt 64-bit library that is 4 KB aligned, so Google Play will block the app's updates from 1 February 2027. We found it by checking the prebuilt libraries of the 259 native packages our test apps use most, and reported it to Expo (expo/expo#51329) and upstream (sqlite-vec#254). The default expo-sqlite build is fine.
0.1.50
9 October 2026
- Upgradesreact-native-push-notification and React Native 0.82. The library calls
getReactNativeHost()when the FCM token refreshes and when a notification action is tapped. From React Native 0.82 that getter throws unlessMainApplicationstill overrides it, and the 0.82 template no longer does. The finding now warns about it before the upgrade. - Behind the scenesWe scanned the Android code of the 259 native libraries our test apps use most, looking for the two patterns that crash under the New Architecture:
@ReactMethodfunctions that return something (react-native-track-player 4.x, now with a fix) and unguardedgetReactNativeHost()calls. Every other hit turned out to be guarded, a codegen override, dead code or an example app. The popular ecosystem is in good shape here.
0.1.49
9 October 2026
- Upgradesreact-native-track-player: what the registries do not tell you. Version 5, the New Architecture rewrite, is a different package (
@rntp/player) under a commercial license. The free 4.x line does not compile with Kotlin 2.1 and crashes at launch with the New Architecture on Android. The finding now says so, and points to our pull request with the fixes (apply it with patch-package until it is released), or to expo-audio for simple playback.
0.1.48
9 October 2026
- AccuracyFace ID with expo-local-authentication is not a crash. Without
NSFaceIDUsageDescription, most biometrics libraries crash on iOS 17+, and that stays high.expo-local-authenticationchecks for the key itself and skips Face ID instead, so it is now a medium "Face ID never shows" finding. - AccuracyVulnerability counts show what reaches a mobile app. axios advisories about proxies,
no_proxy, SSRF and the Node.js HTTP adapter cannot reach React Native, which uses XMLHttpRequest. The title now reads "21 known vulnerabilities (+11 for Node.js only)" instead of 32. - FixReact Native release candidates show their full version (
0.88.0-rc.4), not0.88.0. - Behind the scenesChecked on Expo Go, the Yoroi and Valora wallets.
0.1.47
9 October 2026
- SecurityAI provider keys that ship inside the app. Reading
process.env.EXPO_PUBLIC_OPENAI_API_KEY(or a Gemini, Anthropic, Groq, OpenRouter, Replicate, fal.ai… key) in app code compiles the key into the JavaScript bundle, even though.envis never committed. The same goes forreact-native-configandreact-native-dotenv. Anyone who unpacks the app can run requests on your bill. Reported as high, with a note when the app also calls the provider directly; server folders and Expo API routes are left out. Found in 12 of 869 open-source apps, almost all AI features added in the last year (what we found). - AccuracyA private key in a
.envfile used only by server code (Expo API routes) is reported as committed to the repository, not as shipped inside the app: Expo inlines onlyEXPO_PUBLIC_variables. The public demo keys thatsupabase startgives every developer are no longer reported. - Behind the scenesWe added 148 open-source health and wellbeing apps to the test set and measured a "health data sent to analytics" check on them. It found no real case (most of these apps use no analytics at all), so it is not shipped.
0.1.46
9 October 2026
- AccuracyMixed React Navigation majors: a crash only with two copies of the core. NativeKeel now reads the lockfile (npm, Yarn, pnpm and Bun). If two majors of
@react-navigation/nativeorcoreare installed, navigators run against a different container and crash: still high. With one copy, a navigator from the other major usually runs (a large open-source wallet ships this way), so it is reported as an unsupported mix (medium). - AccuracyWebView file-URL flags on web pages.
allowUniversalAccessFromFileURLsonly matters for pages loaded fromfile://. A WebView that only opens web URLs gets a low "remove the flag" note. Bundled, downloaded or inline HTML keeps the high finding, including when the address is defined in another file the screen imports. - AccuracyLocal fallback keystores. A keystore with a throwaway password (
"password"), used only in theelsebranch when the real signing values come from Gradle properties, is not reported as a leaked release key. A real password in that branch is still reported. - AccuracyLibraries whose native side
react-native.config.jsbuilds from another folder (a shim that links Reanimated 3 on a legacy-architecture Android build) are not checked against the installed version's architecture support.Math.randomin a mock or dummy response is not reported. A private key in a test file is low (a test key pair protects nothing, unless it is reused).
0.1.45
9 October 2026
- AccuracyMonorepo packages are yours, not npm's. In large monorepos (we re-checked three big wallet apps), packages linked with
workspace:,link:,file:orportal:are developed in the same repository. NativeKeel used to look up their name on npm and report an unrelated publish date ("no release since 2023"). They are skipped now. Packages that a pnpmcatalog:pins to an npm version are still checked, because they do come from npm. - FixWording of the Expo SDK step for a single newer package.
0.1.44
9 October 2026
- PerformanceRedux selectors that re-render on every store update.
useSelector(state => ({ ... })), or a fallback likestate.x[id] || {}, returns a new value on every call, so the component re-renders whenever anything in the store changes. Reported with the fix (select values separately,shallowEqual, or a constant fallback). - FixPerformance findings could point at the wrong line in files with block comments. They point at the right line now.
- Behind the scenesWe measured other re-render patterns on 653 apps and did not ship them: effects without dependencies that set state (22 hits, almost all harmless because they set the same value), inline Context values (155 apps, impact depends on how often the provider renders), and Zustand 5 object selectors (no confirmed case; the one hit used a different store library). Real re-render costs need a profiler on a device; we only report patterns that are wrong every time.
0.1.43
9 October 2026
- AccuracyLess noise about general JavaScript utilities. A small, finished utility such as
clsxwas rated like a React Native library when React Native Directory marks it unmaintained. It has no effect on React Native upgrades, so it is now low. Packages tied to React Native stay medium: by name, through areact-nativedependency, or through a sibling in the same scope (@rneui/themedbuilds on@rneui/base). Found while scanning more large open-source apps (wallets and a travel app).
0.1.42
9 October 2026
- AccuracyTested on large open-source production apps. We added well-known open-source apps with millions of users (hardware and crypto wallets, a forum platform) to the test set. They showed two things to fix:
- React Native declared through Yarn's patch protocol (
patch:react-native@npm%3A0.83.4#…) or annpm:alias was read as "no version", so the version checks were skipped and the New Architecture looked off. Both are read now. - Packages newer than the Expo SDK expects were treated like older ones, with
npx expo install --fixas the advice, which would downgrade a version the team chose on purpose. Older versions are still the build and crash risk they were; newer ones are now low (medium for a major) with the right advice: list them inexpo.install.excludeafter testing. Packages already in that list, Expo's own opt-out, are no longer reported.
- React Native declared through Yarn's patch protocol (
0.1.41
9 October 2026
- DocsThe example report in the README, on the homepage and in the share image showed an older "Start here" and security line than the tool prints today. They match again, and a check now compares them with the tool's own output before every release.
- AccuracyTested with dependencies installed on 17 open-source apps that are published in the App Store or Google Play: no new false alarms, and all 79 packages reported as unused were confirmed unused.
0.1.40
8 October 2026
- ExperienceTell us when NativeKeel is wrong. Every report now ends with a link to a short form for a wrong or missed finding. Nothing is sent automatically, and the form asks for the finding's title, not your code. Reports from real apps are how most of this month's accuracy fixes happened.
- AccuracyOn a React Native release candidate ahead of the latest stable (0.88 RC while 0.87 is stable), library compatibility tables do not cover it yet. Instead of calling Reanimated or Screens incompatible, NativeKeel says the tables do not cover it.
- Behind the scenesOur test set now looks first for open-source apps that link their App Store or Google Play page, which have real users: 30 added this week, 94 already in.
0.1.39
8 October 2026
- AccuracyWhen deciding whether a removed React Native API is still used, names inside
/* … */comments (including JSX comments) no longer count as uses.
0.1.38
8 October 2026
- AccuracyRemoved core APIs: used or only imported? An import of
DatePickerAndroid,AsyncStorageand the like from'react-native'was reported as a crash. In release builds such an import is simplyundefined(only development builds throw), so it only fails where the code calls it. NativeKeel now checks whether the name is used beyond the import: if it is, it stays a crash risk; if not, it is a low "unused import, delete it". Found because a production app that works fine was told otherwise.
0.1.37
8 October 2026
- AccuracyLessons from a real production app. NativeKeel was run on a private production app with its dependencies installed. The output showed five things we got wrong, all fixed:
- A prerelease of the next major (React Navigation 8 alpha) was called "a major version behind", and the plan suggested the latest stable: a downgrade. Packages are now "behind" only when npm's latest is newer than what you have.
react-native-edge-to-edgeandreact-native-bootsplashwork through a theme instyles.xml, without an import. They were listed as unused; removing them would break the app's look.- A JavaScript package that ships an empty iOS podspec (
react-native-render-html) was treated as a native module and rated high. - The missing Folly coroutine flag was rated high on an app already on React Native 0.80+, which builds fine. It is now a warning before you move to 0.80, and a low note after.
- A React Native upgrade step asked to move a library that was already in the range it needs.
0.1.36
8 October 2026
- StoreRelease builds signed with the debug key. The React Native template signs release builds with the public debug key, and Google Play refuses the upload ("signed in debug mode"). NativeKeel now reports it when nothing else signs the build: projects built with EAS, or signed in CI with Fastlane or a signing action, are recognised and left alone. 62 apps in our test set. A fix page shows the setup that keeps passwords out of the repository.
0.1.35
8 October 2026
- FixThe npm page showed "What's new in 0.1.33" after 0.1.34 was out. A test now fails the release when the README or this page do not name the version being published, so it cannot happen again.
0.1.34
8 October 2026
- DocsThe GitHub Action gets a shorter description for the GitHub Marketplace, and the npm page a clearer description and keywords. New on the site: React Native fixes, one page per common build error, store rejection and crash, with the cause, the fix and the sources.
0.1.33
8 October 2026
- Experience"Start here" also weighs package replacements and cleanups by severity: an unmaintained native module now comes before a deprecated component that still works.
0.1.32
8 October 2026
- Experience"Start here" leads with what matters most. The three steps at the end of every report used to follow a fixed order of topics, so a minor version mismatch could come before a package with 35 known vulnerabilities. They are now ordered by the most severe finding behind each step, and then by urgency. Crash fixes inside the plan are sorted the same way.
0.1.31
8 October 2026
- AccuracyTested the way you run it: with dependencies installed. Most of our test set is scanned straight from GitHub, without
node_modules. This time we installed the dependencies of 22 recent apps (scripts disabled) and compared both scans. With packages installed NativeKeel sees more, as it should: a second copy of React, patches that no longer match, Kotlin modules that fail on the New Architecture, packages off the Expo SDK. Two things were wrong, and are fixed:- An Expo SDK written as a major only (
"expo": "^54") was not recognised withoutnode_modules, so the app was treated as plain React Native and told its React Native was unsupported. 9 apps in our test set. expo-system-ui,expo-splash-screen,expo-dev-clientandexpo-updateswork fromapp.jsonor register natively, without an import: they were listed as unused. Removing them would break dark mode, the splash screen or updates. The other 44 "unused" packages we checked by hand really were unused.
- An Expo SDK written as a major only (
0.1.30
7 October 2026
- StoreiOS SDKs too old for Apple's privacy manifest rule. Apple lists SDKs (Firebase, SDWebImage, Lottie, GoogleUtilities, Alamofire and others) that must ship a privacy manifest: App Store Connect refuses a new app that includes an old version, or an update that adds one. NativeKeel reads
ios/Podfile.lockand names the React Native package that pulls each one in, since that is what you update: SDWebImage 5.11.1 usually comes fromreact-native-fast-image, old Firebase from@react-native-firebase. The first version with a manifest for each SDK is read from the CocoaPods specs by a script, not typed by hand. 24 of 116 apps with a Podfile.lock in our test set. - AccuracyThe "hermes" on Apple's list is a 2015 Imgur project, not React Native's engine (the React Native team confirmed this with Apple), so React Native's Hermes is not reported.
0.1.29
7 October 2026
- StoreAccount deletion. The App Store requires apps that let people create an account to let them delete it from inside the app (guideline 5.1.1(v)), and Google Play requires an in-app path plus a web link. It is one of the most common rejection reasons. NativeKeel now flags apps whose code signs users up (Firebase, Supabase, Amplify, Appwrite, Clerk or your own
/signupAPI) with no deletion anywhere. Links to another service's sign-up page and device registration are not counted. 43 apps in our test set. - StoreSign in with Apple. Guideline 4.8: an iOS app that uses Google or Facebook login for the user's account must also offer a privacy-focused login, and Sign in with Apple qualifies. Reported with Apple's exceptions spelled out. 11 apps.
- Behind the scenesApp Tracking Transparency was measured and not shipped: without the prompt, ad SDKs simply cannot track, which costs ad revenue but is not a rejection. We only call something a rejection when it is one.
0.1.28
7 October 2026
- StabilityA release build that talks to your laptop. An API address like
10.0.2.2(the Android emulator's name for your computer),192.168.x.x,localhostor an ngrok tunnel, used outside any development-only branch, works on your machine and fails on every user's phone. NativeKeel now finds these and points to the line. Development branches (__DEV__, dev environment flags), settings screens where users enter their own server, named local fallbacks, local-service probes and server-only code are left alone. 21 apps in our test set ship one. - Behind the scenes
evalandnew Functionwere measured too: 9 apps, almost all legitimate (web-only files, debug tools). Not shipped as a check.
0.1.27
7 October 2026
- StoreThe build error waiting behind the target SDK bump. Google Play requires API 36 for updates. Apps still targeting 30 or lower usually have activities or receivers with an intent-filter and no
android:exported; from target 31 that stops the build. NativeKeel lists them and the plan fixes them first, before the target SDK step. 107 apps in our test set would hit this. - Behind the scenesTwo candidates measured and not shipped: missing Android 13 notification permission (10 of 11 apps already request it at runtime, and Firebase Messaging and Notifee declare it for you), and WebViews opening a URL from a deep link (no case in 653 apps). We add a check when real apps show the problem, not before.
0.1.26
7 October 2026
- StabilityPackages Expo did not test with your SDK. Each Expo SDK pins the library versions it is tested with. A native module from another release is one of the most common causes of build failures and launch crashes in Expo apps. NativeKeel now compares every pinned package (not only Reanimated, Screens and Gesture Handler) and rates the gap: a major difference is high, a minor one medium, a patch low. In our test set, 144 of 390 Expo apps with a lockfile have at least one, most often Reanimated, safe-area-context and Screens. The fix is one command:
npx expo install --fix. - StabilityA library bumped ahead of React Native. When a native library declares that it needs a newer React Native than the app has (Clipboard 1.14 needs 0.73, the app is on 0.72), builds commonly fail or the first call crashes. Only lower bounds count: loose upper caps such as
^0.60.0on 0.62 are ignored, since apps run fine with them. - AccuracyA TLS bypass set on
react-native-blob-utilis judged by how requests use it: never used, it is not reported; tied to a setting (trusty: !certVerification, for self-hosted servers), it is high instead of critical. Found while checking well-known open-source apps. - PrivacyIn Expo projects without
node_modules, NativeKeel asks unpkg for the versions your Expo SDK expects, sending only theexpoversion number. The privacy page, README and SECURITY.md list every request.
0.1.25
7 October 2026
- SecuritySupabase tables without row level security. The anon key ships inside every copy of the app, so a table in the public schema without RLS can be read and changed by anyone through Supabase's REST API. NativeKeel reads the migrations under
supabase/and lists the tables that never enable it (a commented-outenable row level securitydoes not count). Tables in other schemas and RLS enabled in a loop are recognised. In our test set: 3 of the 15 apps with Supabase migrations, one of them a starter template with payment and invoice log tables open. - StorePermissions Google Play restricts. Photo and video access (enforced since May 2025: use the photo picker unless your app is a gallery), all files access, app installs, background location, SMS and call log, full-screen intents and exact alarms each need a core use case and a Play Console declaration, or the app is rejected or removed. Permissions you remove with
tools:node="remove"or Expo'sblockedPermissionsare not counted. Each rule was checked on Google Play's policy pages. Found in 24 apps.
0.1.24
7 October 2026
- Accuracy200 more apps, all pushed to GitHub in the last month. Our test set now grows every week from recently updated React Native and Expo apps (653 scanned, zero tool failures). What they showed, now fixed:
- A private key is reported only when there is a key: form placeholders (
-----BEGIN … Paste your key here), elided samples and constants holding just the header line are not keys. Real keys are still found. - Reanimated 4 without
react-native-workletsin package.json is fine when the lockfile has it: npm 7+ and pnpm install peer dependencies on their own. - A test keystore used as a local fallback (
storeFile file('test.keystore'), password123456) is not a release key. - MD5 on a password is low, with an explanation, when it is the Subsonic API's own token format: the app has no choice there.
- A private key is reported only when there is a key: form placeholders (
- ExperienceNo more waiting on a slow network. A scan now spends at most 90 seconds on npm and React Native Directory; if they are slow, the report arrives with a note on what is missing instead of hanging.
0.1.23
6 October 2026
- StabilitySafeAreaView on Android 15. The
SafeAreaViewfrom'react-native'only ever applied to iOS. Apps that target API level 35 or higher (Expo SDK 52+ do) are drawn edge-to-edge on Android 15 and newer, so screens wrapped in it already sit under the status bar there. When your target SDK is 35+, NativeKeel now says so and rates it medium;react-native-safe-area-contextfixes both platforms. 29 apps in our test set are in this situation.
0.1.22
6 October 2026
- SecurityAuth tokens in plain storage, found by what is stored. The check used to look only at the storage key (
setItem('access_token', …)). It now also catches tokens saved under a constant (setItem(TOKEN_KEY, token)) or inside an object (JSON.stringify({ token })). Push notification and device tokens are left alone, and web-only files (*.web.ts) are skipped since the web has no Keychain. In our test set this finds 13 apps instead of 4. - DocsThe homepage and npm page link to what we found in 470 open-source apps.
0.1.21
6 October 2026
- Correction16 KB pages: the right date. NativeKeel said Google Play already rejects updates without 16 KB page support and rated it critical. Google's current page (updated September 2026) says the policy applies since November 2025, Play Console warns now, and Play blocks updates from 1 February 2027. Until then the finding is high, with that date; from 1 February 2027 it becomes critical on its own. Found by our upstream check, which now also watches this date.
0.1.20
6 October 2026
- UpgradeAPIs React Native has announced it will remove. React Native 0.87 deprecated
ImageBackground,DrawerLayoutAndroidandUTFSequence(and 0.81SafeAreaView): they still work and log a warning, and once removed, every screen that imports them crashes. NativeKeel now lists where you use them and what to use instead. In our test set, 139 of 470 apps import at least one, most oftenSafeAreaVieworImageBackground(how to migrate). - StoreThe Google Play target SDK message knows when the extension period ends (1 November 2026) and stops mentioning it afterwards.
- Behind the scenesWe now check upstream on a schedule: new React Native and Expo releases, the libraries' compatibility tables, what each Expo SDK pins, what React Native deprecates, and Google Play's policy page. This release came from that check.
0.1.19
6 October 2026
- PlanBetter plans for apps that are far behind. On an old React Native (0.62, say), the step before the upgrade no longer suggests the newest release of each library, which usually needs a much newer React Native. It asks for the newest release that supports your version and shows the latest for reference. Reanimated, Gesture Handler and Screens are left to the React Native steps, which pick tested versions for each hop.
- PlanSecurity steps for packages that the React Native upgrade moves anyway (React Native itself, Reanimated) say so, and when to update them early: if you ship before reaching those steps.
0.1.18
6 October 2026
- Security"No fixed release" is said plainly. When the vulnerable range includes the newest published version (expr-eval 2.0.2, for example), the plan no longer says "update". It says no fix exists: replace the package, or make sure it never handles untrusted input. When the advisory only says "up to 4.17.23", the version to install is now the actual next release (lodash 4.18.1).
- PlanLibrary updates that fit your current React Native. Before the React Native steps, the plan used to suggest the newest Reanimated or Gesture Handler even when it needs a newer React Native. It now stops at the newest version your current React Native supports, and the React Native steps move them further.
- PlanFamilies move together. All
@react-navigation/*packages (and all@react-native-firebase/*) are one step, since mixed major versions crash at runtime. React Navigation is no longer mistaken for a native module, and renamed community packages (such as@react-native-community/masked-view) are recognised as native even withoutnode_modules, so the plan says "swap it" instead of "replace it some day". - PlanHermes appears in one step, not two, and version ranges read "2.32+ (2.x line)" instead of "2.32–2.99.x".
- FixThe HTML report showed bold plan steps as
**text**. It now renders them in bold.
0.1.17
6 October 2026
- SecurityEvery vulnerable package now says which version fixes it. Advisories written as "up to and including 1.13.4" were not read, so a package with 35 advisories showed "check the advisories" instead of "fixed in 1.20.0". It is now in the title and in the plan step. 378 of 381 vulnerable packages in our test set get a fixed version.
- AccuracyMore advisories that cannot reach a mobile app are counted as low: axios' HTTP/2 adapter, proxy and
NO_PROXYhandling, server-side request forgery and cloud metadata leaks. They stay visible in the details. - ExperienceLess noise in Expo apps. Packages whose version the Expo SDK decides (
expo-*, Reanimated, Screens, AsyncStorage, …) no longer appear one by one as "a major version behind". They are one line: "19 packages move with the Expo SDK upgrade", sincenpx expo install --fixmoves them. Across our test set, 3,700 low findings became that one line.
0.1.16
6 October 2026
- SecurityDeep links. Web links (
https://your.domain/...) that are not verified withautoVerify: Android 12+ opens them in the browser instead of your app, and older Android lets any app that registers the same links receive them, including login, reset and invite links. And the template URL schememyapp://, which 72 of the 470 apps we scan still ship: another app with the same scheme can open your links, and catch your sign-in redirect when you use expo-auth-session, Clerk or AppAuth. Both under MASVS-PLATFORM. - AccuracyTested on 180 more open-source apps (450+ in total, zero tool failures). Fixed what they showed:
.DS_Storefiles caught in a patch are no longer reported as "build output that will not apply", and keystores inside test fixtures are not release keys. - ExperienceThe HTML report wraps long file paths and code on phone screens.
0.1.15
6 October 2026
- ExperienceMonorepos. Run at the root of a monorepo and NativeKeel lists the app folders to scan (
npx nativekeel apps/mobile) instead of stopping with "not a React Native app". Libraries are not suggested. - PlanAn app that needs no React Native or Expo upgrade gets an Action plan, not an "Upgrade plan".
- DocsThe README and npm page list every check by group: upgrade, store, crashes, security (by OWASP MASVS) and performance.
0.1.14
6 October 2026
- SecuritySecrets in Expo config. Secret-looking values in
app.json/app.configextraand inEXPO_PUBLIC_variables ship inside the app; secrets ineas.jsonbuild env are committed to the repo (found a Sentry auth token this way in two open-source apps). Public SDK keys such as RevenueCat's are left alone. - StabilityAPIs removed from React Native core.
AsyncStorage,Picker,Slider,WebView,ViewPropTypesand 23 others imported from'react-native'throw or are undefined on current versions. Reported as a crash now when the installed version already removed them, or as a step before the upgrade, with the replacement package for each. The list comes from React Native's own source.
0.1.13
6 October 2026
- PerformanceSpeed up the app. A new plan phase for the static signs of jank and weight: a FlatList inside a ScrollView that renders every row, animations driven from the JavaScript thread, console logs left in release builds, whole-library imports of lodash and moment, and oversized images the app actually requires (repo screenshots are not counted).
- SecurityReverse engineering. Source maps packaged into the app (they give back your original code), and release builds with Hermes or R8 off. Reported honestly: obfuscation only slows an attacker down, so secrets and trust decisions belong on the server. A new MASVS-RESILIENCE group in the security overview.
0.1.12
5 October 2026
- SecurityHacking risks, mapped to OWASP MASVS. Every security finding now names its MASVS group, and reports show a security overview: which groups were checked and how many issues each has.
- SecurityOpen Firebase rules. Realtime Database, Firestore and Storage rules that let anyone read or write, root rules that give every signed-in user everything, and test-mode rules (open until a date, or expired). Public folders such as event images are left alone.
- SecurityTLS certificate checks turned off. Trust-all managers, hostname verifiers that accept everything, WebViews that proceed on SSL errors and iOS sessions that trust any server. A bypass behind a "trust my self-signed server" setting is reported as such, at lower severity.
- SecurityWeak cryptography and token storage. Hardcoded encryption keys, MD5/SHA-1 on passwords, ECB mode, Math.random for nonces and salts, auth tokens in AsyncStorage.
- AccuracyDependencies installed from git are never matched against npm advisories (a wallet app was flagged with a malware advisory that belongs to a different package with the same name).
0.1.11
5 October 2026
- FixThe GitHub Action works. A colon inside one input description made
action.ymlinvalid, souses: AlicanAkyol/nativekeel@v0failed to load. It is fixed, the Action now has anexit-codeoutput, and a workflow runs it on a sample app on every change so this cannot slip again.
0.1.10
5 October 2026
- ExperienceStart here. Every report now opens with the three most urgent first steps (leaked keys, crash risks, store deadlines, security gaps), in the terminal and in the HTML report. On the real app our case study is based on, it picked the same three priorities we had reached by hand.
- StabilityMissing iOS permission texts. Using the camera, photos, location, microphone, contacts, calendars, Bluetooth or Face ID without the matching Info.plist description makes iOS close the app and App Review reject it. Expo config plugins are taken into account.
- PlanStore deadlines (target SDK, 16 KB pages, privacy manifest) now sit together at the start of the plan.
0.1.9
5 October 2026
- SecurityAndroid components open to every app. Services, receivers and providers exported without a permission. Widgets and receivers for system broadcasts are left alone, because Android needs them exported.
- SecurityAPI calls over plain HTTP. fetch, axios and WebSocket calls to real hosts over http:// or ws://; local addresses and links opened in the browser are ignored.
- ExpoOld Expo projects (SDK 44 and earlier) are read correctly: React Native comes from Expo's fork, and the plan uses the right upgrade command for each SDK (the legacy CLI before SDK 46). For very long jumps it also weighs starting a fresh project.
0.1.8
5 October 2026
- SecurityKnown vulnerabilities in what you ship. Advisories from the GitHub Advisory Database for the exact versions in your lockfile or node_modules (npm, yarn, pnpm). Advisories that only affect Node.js servers stay visible at low severity instead of raising false alarms.
- SecurityPasswords leaking into logs and databases. Follows a password through intermediate variables into crash reports, analytics, remote database writes or plain AsyncStorage. Built from a real leak we found in a production app.
- SecurityUnsafe WebViews and Android backups. WebViews that let page scripts read local files or mix HTTP into HTTPS;
allowBackupwithout backup rules. - StabilityCrash risks. Reanimated without its Babel plugin or react-native-worklets, mixed Firebase or React Navigation majors, a second copy of React or React Native inside a dependency.
- PlanNew phases: Fix crash risks and Close security gaps.
0.1.7
4 October 2026
- PlanFor old apps, library versions recommended before the New Architecture switch now run on the legacy architecture, each library stays on its major line, and forced major migrations are flagged.
- PlanRenamed community packages (async-storage, cameraroll, masked-view, viewpager, picker, clipboard, netinfo) get a "swap and update imports" step.
- ReportsThe HTML report folds outdated packages into one table; GitHub code scanning links work for folders with spaces.
0.1.6
4 October 2026
- PlanUpgrade plans reviewed line by line on real apps. The Google Play 16 KB deadline is now explicit; managed Expo apps get EAS commands instead of android/ios ones; abandoned JavaScript packages no longer pose as upgrade blockers; a nearly current app is no longer sized like a migration.
- AccuracyPatched packages, alias fields and Node core polyfills are never reported as unused.
0.1.5
4 October 2026
- PlanApps older than React Native 0.76 now get the New Architecture switch at the right point of the upgrade (it was treated as already on).
- PlanExpo: SDK-managed packages move with
npx expo install --fix, never bumped past the SDK. - AccuracyReanimated compatibility is generated from Reanimated's own data; the iOS privacy manifest is recognised as generated by React Native 0.75+; npm rate limits are retried and reported instead of silently missing checks.
0.1.4
4 October 2026
- AccuracyFirst run against 32 open-source apps: 11 fixes, from piped JSON output being cut off to placeholder secrets reported as real.
- Monorepospnpm and Bun catalog versions are resolved.
0.1.3
4 October 2026
- PlanEvery upgrade plan starts with a safety net: UI flows on both platforms before the first change. On a real upgrade they caught a post-login crash, a frozen sign-up and an invisible button.
0.1.2
4 October 2026
- StabilityNew known issue from a real upgrade:
react-native-linear-gradient2.x around a Modal crashes on the New Architecture.
0.1.0 – 0.1.1
3 October 2026
- First release: support status, New Architecture blockers, Google Play target SDK and 16 KB pages, iOS privacy manifest, 14 secret patterns, unused packages, upgrade plan, HTML/Markdown/SARIF/JSON output, baseline for CI and a GitHub Action. Published with npm provenance.