NativeKeel

NativeKeel

Health check for React Native and Expo apps. One command, no install, no account:

npx nativekeel

No terminal handy? Paste your package.json at nativekeel.com/check: the same dependency checks and upgrade plan, run in your browser.

Works with GitHub Actions (a quality gate comment on every pull request), SonarQube (findings in your existing projects and quality gate) and AI coding agents (MCP server for Claude Code, Codex and Cursor). Several apps? npx nativekeel fleet puts them on one page.

What's new in 0.1.122: clearer MCP tool descriptions, so AI agents choose between health check, security review, improvement plan and upgrade tools correctly. 0.1.121: known malware anywhere in your lockfile's dependency tree (supply-chain attacks such as the October 2026 Shai-Hulud worm in tensorlake), not only in package.json: critical, cannot be ignored, and stops install. 0.1.120: the upgrade catalog reaches back to React Native 0.85 — StyleSheet.absoluteFillObject removal and the @react-native/jest-preset move are now reported for apps a few versions behind (146 and 133 of 1,162 open-source apps use them). 0.1.119: the upgrade breaking-change catalog audited against the official release notes — three more React Native 0.87 changes caught (react-native/src/private/ imports, DrawerLayoutAndroid, @react-native/assets-registry), and 0.88 confirmed to have no breaking changes. 0.1.118: detects the critical, actively-exploited Metro development-server command injection (CVE-2025-11953) from a vulnerable @react-native-community/cli in your lockfile — even when it is only a transitive dependency. 0.1.117: npx nativekeel upgrade — a go/no-go for the newest React Native / Expo: what breaks in your own code and dependencies with file and line, a READY / NOT READY / multi-version-jump verdict, exit 1 when blockers remain so CI can gate the upgrade PR, and the MCP tool upgrade_readiness. 0.1.116: a reliability release: the SARIF export no longer stops on findings with several locations, the pull request gate also fails on findings that got worse or spread to new files, files loaded by require.context or a computed import are no longer called unused, and a console.log no-op no longer hides console.info calls. 0.1.115: the SonarQube export no longer fails on findings located as file:line and maps issues to their real file; every finding says what its evidence rests on; the HTML report is grouped by what to do; exceptions can expire (until); measured accuracy. 0.1.114: Supabase policy checks read far more real migrations (28 of 45 open-source databases, up from 8): pg_dump settings, cron calls, column changes and DO … CREATE POLICY blocks no longer stop them. 0.1.113: script injection in GitHub Actions (an issue or pull request title pasted into a run: script in a workflow that has secrets). 0.1.112: "gate" in chooses which checks can fail the build; findings in code the app never imports are labelled and lowered. fewer false alarms from a production app review: inherited AppDelegate window, Folly flags set in the Podfile, release logging silenced by a project's own Babel plugin or a run-time no-op, server-only moment advisories; the 16 KB finding says which build it measured. database reads opened too widely (Firestore collections of people or private records readable by any signed-in user, Supabase tables of people with email or phone readable by anyone) and public storage buckets with private names. GitHub Actions workflows that run a fork's pull request with your secrets ( + checkout + run), the mistake that exposed Jellyfin's App Store credentials. URLs trusted after a text comparison ( also accepts ), subscriptions or roles the app writes to its own database, login tokens sent to other sites; and cleanup: source files nothing imports, unreferenced images, backup copies, statements. Sentry auth tokens, secrets in an Expo reported as shipped (Expo embeds the config), and more server secrets read by app code (AWS, Cloudinary, Twilio, email APIs, any ); checked against 10 published vulnerabilities (found 5 → 7). keys added at build time (EAS or CI environment variables) are found by scanning the built app's JavaScript bundle, Hermes bytecode included: automatically under , or . timers and listeners that can never be stopped, request loops, and credentials in release logs; tested against an app with 41 known problems (found: 59% → 76%). in the HTML report, outdated packages are listed right after the other low findings and the low card says how many there are. files in no longer produce code findings (secret checks still read them), Metro's is recognized, and react-native-gesture-handler buttons get the accessibility checks. every finding shows its id (for ), leaves out folders that are not part of the app, files encrypted with git-crypt are no longer reported as committed secrets, and logging inside is no longer counted. fewer false alarms for React header imports that only compile on the old architecture, and the list: 18 of the 590 most used native libraries break on 0.87/0.88. clearer MCP tools: every parameter documented, standard read-only annotations on all eight tools. backend admin credentials compiled into the app (Supabase service_role, Hasura admin secret, Firebase service accounts, database passwords, Stripe secret key) and server-only SDKs imported by app code. fewer false alarms: React header imports in an app's own AppDelegate or bridging header are no longer reported on React Native 0.87 (they resolve in the app target; only libraries fail). render loops ("Too many re-renders", "Maximum update depth exceeded") found with file and line: handlers called instead of passed, effects that set state on every run. a React Native version that does not match the Expo SDK is reported (a common cause of build failures and launch crashes). Google Play's API 36 requirement (extension ends 1 November): the edge-to-edge opt-out Android 16 ignores, and orientation locks tablets and foldables ignore. team panel (closed beta): sends a scan summary (no code) to your team's page with history and trends; GitHub Action input . . puts NativeKeel findings inside SonarQube (generic issue import, tested on Community Build 26.10), also as the GitHub Action's input (). React Native 0.88 and Expo SDK 58 are stable: the UIScene finding gives 0.88's official SceneDelegate steps, and (deprecated in 0.88) is reported with its replacement. shows what changed per app since an earlier run (ratings and critical/high counts), plus new and removed apps; includes ratings. pull request comments start with a quality gate and show the A–E ratings with what changed; a committed holds the team's gate level and accepted findings (each with a reason). every report rates Security, Store, Stability, Upgrade, Performance and Accessibility from A to E, and shows all your apps in one table, worst first, with their ratings and store deadlines ( for a shareable page). libraries whose iOS code no longer compiles on React Native 0.87 ( instead of ) are found in your installed packages before the upgrade, and reported as the cause after it (); on 0.87+ is reported as a crash. when a report has a store or end-of-support deadline (Play target SDK, 16 KB pages, Xcode 27 UIScene, unsupported React Native or Expo, New Architecture off), it ends with one line on where to ask if your team can't fit the upgrade in time. a page for the React Native 0.77+ error "RCTEventEmitter.receiveEvent() ... has not been registered as callable" with the AppDelegate fix for Objective-C and Swift (), linked from the finding that detects it. the AppDelegate-window crash finding links to a new page listing each affected library and its fix (); reports point to Expert help instead of the old pricing link. : paste a package.json and get the dependency checks and upgrade plan in your browser, with the same rules as the CLI. the GitHub Action can keep one comment on each pull request up to date with the findings that pull request adds or fixes (). no longer reports unchanged committed signing keys and passwords as new. compares two release builds: which packages were added or removed, which grew, and which started being bundled twice (one showed up as +107 KB). Also in the MCP tool . the bundle measurement reaches the rest of the report and AI agents: lodash and moment findings say how many bytes they really take in your release bundle (or that they are not in it), and the MCP tool returns the per-package breakdown. : the release JavaScript bundle measured from its source map, per package, including packages bundled twice. Works with Hermes bytecode maps; nothing is built or run. fewer false alarms: push-notification and invitation tokens are no longer reported as unencrypted auth tokens, even when the storage key is a constant, and large JSON required inside a function is described as bundled but evaluated only when used. OTA updates: a note when expo-updates relies on a hand-written runtime version or the appVersion policy (59 of 871 apps), and react-native-code-push now says that App Center is gone and Microsoft archived its CodePush server. iOS file sharing that puts an unencrypted MMKV, expo-sqlite or Realm database in the Files app and Finder. biometric unlocks that only check a yes/no in JavaScript, with no secret bound to Face ID/Touch ID/fingerprint (41 of 871 apps, wallets among them); apps that bind a key in JS or native code are not flagged. placeholder text is checked for contrast too ( against the input or the view behind it): 226 placeholders in 55 of 871 apps. large JSON imported into the JavaScript bundle (all translations up front, Lottie JSON that could be a asset) in 19 of 871 apps, and a note on touchables without . text contrast: where a Text color and the background behind it are both literal colors in the code, pairs below WCAG 2.2 AA (4.5:1, or 3:1 for large text) are reported. Found in 180 of 871 open-source apps. buttons whose tappable area is certainly under 44×44 points (explicit size or a bare small icon) and have no : 209 of 871 open-source apps. accessibility checks: icon-only buttons without a label, unlabeled text fields, app-wide text scaling turned off, and that React 19 ignores. On 871 open-source apps, 282 have at least one unlabeled icon button. in , AI keys shipped in the bundle are contained like other exposed credentials, signing keys get signing-specific steps, and upgrade work has its own group. a package.json entry that is not a valid package name (a typo or a workspace alias) is skipped with a warning instead of stopping the scan; the improvement plan gives New Architecture steps for apps before 0.76. and MCP turn existing findings into a prioritized app improvement plan. Exposed credentials get containment steps; dependency usage and performance signals require context and verification. Static patterns do not establish measured speed or size savings. the Codex plugin works again without configuration: Codex cannot pass environment variables to a plugin's server, so its boundary is your home folder (or only on a server you configure yourself). six native Android source checks: archive paths reaching file writes, incoming nested Intent launches, caller-selected WebView URLs, Intent text reaching SQL, and caller-selected file reads/writes. Explicit exported entry points are correlated with Java/Kotlin source and literal Gradle namespaces; findings state OS protections, prerequisites and verification steps. and MCP : a focused review of data exposure, account access and code execution risks. Eight new checks trace credentials into telemetry/URLs, external input into eval/SQL, unsafe OAuth settings and broad private FileProvider paths. Findings show evidence, attacker prerequisites, a fix and a verification step; zero findings never certifies security. stricter MCP file boundaries, validated dependency names, and malware stop warnings preserved across scan, plan, error and verify tools. New checks flag Firebase writes guarded only by sign-in and unconditional Supabase row policies. These are source findings, not proof of deployed exploitability. Plugin servers now require explicit . a Codex plugin () with the MCP server and the same skill as the Claude Code plugin. and the MCP tool: after an upgrade, what got fixed and what is new compared with the last commit; exits 1 on new critical or high findings. and the MCP tool: what a build, launch, crash or store-review error means, the fix, and where your project is affected. the upgrade plan lists what changes in the next React Native and Expo versions in your own code. a Claude Code plugin () that adds the MCP server and tells Claude when to use it, one-click install for Cursor and VS Code. warns before you run a project with planted malware (a VS Code task that runs on folder open, code hidden after a long run of spaces in babel.config.js, JavaScript disguised as a font), the trick behind fake job tests sent to developers. Found in 4 open-source repositories during our weekly scan. listed in the official MCP Registry (). Recent releases added a list in every report, hacking risks mapped to OWASP MASVS, crash and performance checks. Every check is tuned on 850+ open-source React Native and Expo apps, with recently updated ones added every week, to keep false alarms out ().

Summary  4 critical · 4 high · 6 medium · 6 low
Security (OWASP MASVS)  crypto 1 · network 1 · code 1  ·  7 finding categories; not a compliance verdict

Start here
  1. Revoke the AWS access key ID in src/App.js:6 at the provider today.
  2. Set targetSdkVersion = 36 and compileSdkVersion = 36 in android/build.gradle.
  3. Replace @react-native-community/push-notification-ios: no New Architecture support, unmaintained.

Could someone steal data or abuse the app?

npx nativekeel security . --html security.html --fail-on high

Review secrets, credential leaks, backend access rules, unsafe code execution, transport and dependency risks in one report. New flow/configuration findings show where the input enters, where it is used, what an attacker would need, and how to verify the fix. --offline keeps the scan offline and skips online advisory checks. No source code is uploaded.

Keys added at build time. An EXPO_PUBLIC_ value set in EAS or a CI secret never appears in the repository, so no source scan can see it, yet it ships in the app. NativeKeel also opens the built app and scans the JavaScript bundle inside it, plain JavaScript or Hermes bytecode: APKs and AABs under android/app/build/outputs, eas build --local results, committed bundles, and any APK, AAB or IPA you pass with --artifact app.apk (the GitHub Action's artifact input, after your build step).

This is source analysis, not a live attack or a security certificate. Security checks and scope · Mobile flow details · Native Android details.

What it checks

Upgrade

• Is your React Native / Expo version still supported? React Native supports the latest three minors; in Expo projects React Native moves with the SDK.
• Can you upgrade at all? The legacy architecture was removed in 0.82. If the New Architecture is off (it is off by default before 0.76), you are stuck at 0.81.
• Which packages block the upgrade? Native modules without New Architecture support (cross-checked with the package's own codegen spec), unmaintained or with no release in years, with verified alternatives and renamed packages. Library versions for each step come from the libraries' own compatibility tables.
• Which packages might be unused? Installed packages with no import, native reference, requirement or patch found. Listed for review, not automatic removal: dynamic and generated usage can hide from a static scan.

Store

• Will Google Play and the App Store accept your next build? targetSdk, permissions Google Play restricts (photo/video, all files, background location, app installs, SMS), 16 KB memory pages (it also opens your built APK/AAB and checks every native library), the iOS privacy manifest and SDKs too old to have one, missing Info.plist usage descriptions, sign-up without account deletion, social login without Sign in with Apple, and release builds signed with the debug key.

Crashes

• Will it crash at runtime? packages off the versions your Expo SDK expects, release builds that still point at a development server, native libraries that need a newer React Native, Reanimated without its Babel plugin or react-native-worklets, mixed @react-native-firebase/* or @react-navigation/* majors, a second copy of React or React Native inside a dependency, Kotlin modules that cannot load through the New Architecture interop layer, AppDelegate setups that crash in Release, camera/photos/location access without the Info.plist text iOS requires, imports of APIs removed from React Native core (AsyncStorage, Picker, ViewPropTypes, …) or deprecated for removal (ImageBackground, SafeAreaView), and traps learned from real upgrades.

Security, grouped by OWASP MASVS

• Secrets in the app or the repo: AWS, Stripe, OpenAI, Anthropic, GitHub, Slack, SendGrid, Twilio, Shopify, Google OAuth and Supabase service_role keys, private keys, .env values compiled into the bundle, Expo extra/EXPO_PUBLIC_/eas.json secrets, signing keys and passwords.
• Data on the device: iOS file sharing (UIFileSharingEnabled) that exposes an unencrypted MMKV, expo-sqlite or Realm database (they live in Documents by default on iOS), passwords that flow into crash reports, analytics, databases or plain AsyncStorage (followed through variables), auth tokens in unencrypted storage, Android backups that copy them.
• Network: TLS certificate checks turned off in native code, cleartext HTTP, NSAllowsArbitraryLoads, plain-HTTP API calls, user-installed CAs in release.
• Backend rules: Firebase Realtime Database, Firestore and Storage rules open to anyone or in test mode; Supabase tables created without row level security; sign-in-only Firebase write rules and unconditional Supabase UPDATE/DELETE policies without row ownership checks. Policy findings include file/line evidence and explain deployment/grant assumptions.
• Authentication: biometric prompts (Face ID, Touch ID, fingerprint) whose success is only a yes/no in JavaScript, with no secret bound to biometrics in the keychain/keystore, in JS or native code: the prompt guards the screen, not the data.
• Cryptography: hardcoded encryption keys, MD5/SHA-1 on passwords, ECB mode, Math.random for nonces and salts.
• Platform: WebViews that read local files or load HTTP into HTTPS, Android components any app can start, unverified deep links and the template myapp:// URL scheme.
• Dependencies and reverse engineering: known vulnerabilities in the exact versions you ship (GitHub Advisory Database), source maps in the app, Hermes or R8 off.

These are static checks: they catch the common, detectable mistakes, not everything a penetration test of the running app and backend would.

Performance

• What is your release bundle actually made of? npx nativekeel bundle reads the source map a release build already wrote (Android: android/app/build/generated/sourcemaps/react/release/, Expo: npx expo export --dump-sourcemap) and measures how much of the shipped code is your app and each package, and which packages are bundled twice. --base old.map compares two builds: what was added, removed or grew. Nothing is built or run; the normal scan picks the map up too.
• Where should you investigate performance? Nested list patterns, JavaScript animation settings, source logging calls, root lodash/moment imports, referenced images over 500 KB, JSON over 300 KB imported into the JavaScript bundle (every language's translations, Lottie animations), and selector allocation patterns. Confirm the actual components, release output and runtime behavior before changing them; these checks do not measure frame rate, startup time or savings. Accessibility
• Can everyone use it? Icon-only buttons with no accessibility label (VoiceOver and TalkBack say just "button"), buttons smaller than 44×44 with no hitSlop, text and placeholders whose color and background (both set in the code) fall below WCAG contrast, text fields with no label or placeholder, and text scaling turned off for the whole app. Text.defaultProps is flagged too: React 19 (React Native 0.78+) ignores it in JSX, so app-wide fonts and font-scaling limits silently stop applying. Only React Native's own touchables and inputs are checked; custom components, focus order and color contrast still need a test with a screen reader.

App improvement review

npx nativekeel improve /path/to/app --offline
npx nativekeel improve /path/to/app --offline --out IMPROVE.md

Existing security, stability, performance, store and dependency findings become an ordered plan with reasons, applicability conditions, actions, verification and recovery. Exposed credentials get containment instructions. Apparently unused dependencies are review candidates: direct, transitive, dynamic, native and generated consumers must be considered before removal. Performance signals are not measurements.

Use --json for structured output or MCP improve_app. Malware findings block execution-dependent actions. Unknown runtime, backend, accessibility and reliability coverage stays explicit. This adds a decision layer over existing checks, not new vulnerability detectors. See scope and next modules.

Usage

npx nativekeel [path]              # report
npx nativekeel plan --out UPGRADE.md   # step-by-step upgrade plan
npx nativekeel --html report.html  # shareable HTML report
npx nativekeel --markdown pr.md    # summary for a pull request comment
npx nativekeel --sarif nk.sarif    # GitHub code scanning
npx nativekeel --sonar nk-sonar.json  # SonarQube external issues
npx nativekeel --json              # machine-readable output
npx nativekeel --fail-on high      # exit 1 on high or critical (default: critical)
npx nativekeel --offline           # no network at all, local checks only
npx nativekeel --verbose           # list every outdated package
npx nativekeel fleet ~/clients     # every app in a folder side by side

Everything is free. The scan exits with code 1 when it finds a critical issue, so it can gate CI.

Upgrade plan

nativekeel plan turns the report into ordered work: stop leaks, set up a safety net of UI flows, fix crash risks, meet store deadlines, close security gaps, replace blocking packages, switch on the New Architecture at the right point, then upgrade React Native (or the Expo SDK) in small, reviewable hops with links to the Upgrade Helper diffs and the library versions each hop needs. Performance fixes and routine updates come last.

GitHub Action

# .github/workflows/nativekeel.yml
name: NativeKeel
on: [pull_request]
permissions:
  contents: read
  security-events: write   # only needed with sarif: true
jobs:
  health:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: actions/setup-node@v7
        with: { node-version: 20 }
      - run: npm ci
      - uses: AlicanAkyol/nativekeel@v0
        with:
          fail-on: critical
          baseline: .nativekeel-baseline.json   # optional
          sarif: true                           # findings inline in the PR

The report is added to the job summary. To also keep one comment on each pull request up to date with what that pull request adds or fixes, give the job pull-requests: write and set pr-comment: true:

permissions:
  contents: read
  pull-requests: write
# …
      - uses: AlicanAkyol/nativekeel@v0
        with:
          pr-comment: true

The comment compares the pull request with its base commit (no code runs) and is edited in place on every push, not repeated. Pull requests from forks get a read-only token, so they get the job summary only.

With a baseline, only findings that are new since the baseline fail the build:

npx nativekeel --save-baseline .nativekeel-baseline.json   # commit this file

Use with AI coding agents (MCP)

Let Claude Code, Codex, Cursor, VS Code or any MCP client ask NativeKeel what is wrong with a project, how to upgrade it, and which version of a library works with your React Native version, instead of guessing. With it installed, the agent checks the project before it upgrades React Native or Expo, adds a native library, prepares a store release, or runs a project you did not write.

Claude Code (plugin: the MCP server plus a skill that tells Claude when to use it):

claude plugin marketplace add AlicanAkyol/nativekeel
claude plugin install nativekeel@nativekeel

Or the MCP server alone: claude mcp add nativekeel -- npx -y nativekeel@latest mcp

Codex (plugin: the MCP server plus the same skill):

codex plugin marketplace add AlicanAkyol/nativekeel
codex plugin add nativekeel@nativekeel

Or only the MCP server, in ~/.codex/config.toml:

[mcp_servers.nativekeel]
command = "npx"
args = ["-y", "nativekeel@latest", "mcp"]

Any other agent, no MCP needed: add this line to your project's AGENTS.md or CLAUDE.md:

Before upgrading React Native or Expo, adding a native library, or preparing a store release, run `npx -y nativekeel@latest --json` and fix the critical and high findings first.

Also listed in the official MCP Registry as io.github.AlicanAkyol/nativekeel.

Tools: scan_project (findings with file:line and fixes), measure_bundle (what the release bundle is made of, from its source map), upgrade_plan (ordered steps), check_library (latest version, New Architecture support, maintenance, the range that works with a given React Native version, known traps) explain_error (what a build, launch, crash or store-review error means, the fix, and where this project is affected) and verify_upgrade (after an upgrade: what got fixed and what is new compared with the last commit). Without MCP: npx nativekeel explain "<error>" --path . and npx nativekeel verify. The server is read-only and only scans folders under the directory it was started in, plus NATIVEKEEL_MCP_ROOTS (set it when your client starts servers from another folder). Results omit source files and non-package project names. Common instruction-like patterns are filtered, but this is not a complete prompt-injection defense. Malware findings stop upgrade plans; verify_upgrade.ok means no new serious findings, while safety.blocked separately reports current malware. Servers started inside a plugin folder (Codex) use your home folder as the boundary, or only NATIVEKEEL_MCP_ROOTS when it is set. See SECURITY.md.

Ratings and several apps at once

Every report rates six areas from A to E, the way SonarQube rates code: Security, Store, Stability, Upgrade, Performance, Accessibility. A means the scan found nothing in that area, B only low findings, C medium, D high, E at least one critical. A rating describes what the scan found, not a guarantee.

npx nativekeel fleet [folder ...] scans every React Native and Expo app under the folders you give it (client projects side by side, or all apps in a monorepo) and 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. --html fleet.html saves it as a page you can share, --markdown and --json work too, and --fail-on applies across all apps.

npx nativekeel fleet ~/clients --html fleet.html --brand "Acme Mobile"
npx nativekeel fleet ~/clients --json > fleet-2026-10.json     # keep this month's run
npx nativekeel fleet ~/clients --base fleet-2026-10.json       # next month: what changed per app

With --base, every app shows what changed since that run ("Security D→B, critical 2→0"), and new or removed apps are listed. npx nativekeel compare before.json after.json does the same for one app, ratings included.

Every app in a GitHub organization, monthly: copy examples/fleet-workflow.yml to .github/workflows/ in any repository of the organization. On the 1st of each month it clones the repositories on the runner, scans them, compares with last month and writes the table to the run summary, with fleet.html and fleet.json kept as the run's artifact. Private repositories need a read-only FLEET_TOKEN secret; NativeKeel uploads nothing.

Already on SonarQube? npx nativekeel --sonar nativekeel-sonar.json writes the findings in SonarQube's generic issue format; pass it to the scanner with -Dsonar.externalIssuesReportPaths=nativekeel-sonar.json (or set sonar: nativekeel-sonar.json on the GitHub Action). Security findings arrive as vulnerabilities, store rules and crash risks as bugs, upgrade and other findings as code smells, each on its file and line. Tested on SonarQube Community Build 26.10. Details: nativekeel.com/sonarqube.

In a pull request, the GitHub Action's comment (pr-comment: true) starts with a quality gate (passed when the change adds no critical or high finding) and the ratings, with what changed.

A .nativekeel.json next to package.json keeps the team's decisions in the repository: the gate level, findings the team has accepted, folders that are not part of the app (a web dashboard, a backend), each with a reason, which checks may fail the build (gate), and an until date on an accepted finding so it comes back for review: teams usually start by gating only the checks they have seen to be right in their code, and keep the rest as a report. Every finding in the report shows its id in brackets. A finding in a file no import reaches is labelled "in code no import reaches"; crash, performance and accessibility findings there are lowered, security findings keep their level, and a project that loads files by a computed path (require.context, import(variable)) gets no such label at all. --fail-on still wins. Ignored findings stay listed in the report, and malware warnings cannot be ignored.

{
  "failOn": "high",
  "gate": ["secret:*", "backend-admin-in-bundle:*", "ci-*", "android-16kb-libs"],
  "ignore": [
    { "id": "flipper", "reason": "Removed in the 0.80 upgrade, sprint 42" },
    { "id": "a11y-small-touch-target*", "reason": "Design review in November", "until": "2026-12-01" }
  ],
  "exclude": [
    { "path": "tools/admin-web", "reason": "Internal web dashboard, not shipped in the app" }
  ]
}

Team panel (closed beta). With --upload (or the Action's panel-token input) and your team's token in NATIVEKEEL_TOKEN, each scan sends a summary to your team's page on nativekeel.com: app name, versions, ratings, finding titles. No source code and no finding details; never with --offline. Live demo · join the beta: [email protected].

Looking after many apps? Tell us what your team needs: [email protected]

Reports for clients

Agencies can put their own name on the HTML report: npx nativekeel plan --html plan.html --brand "Acme Mobile".

Why you can run this on private code

• Your code never leaves your machine. The only requests are package-name lookups on npm and React Native Directory, and one request to npm's advisory endpoint with the names and exact versions of your runtime dependencies (what npm audit sends). In Expo projects without node_modules, one request to unpkg for the versions your Expo SDK expects (only the expo version is sent). --offline makes none; a test traps fetch to prove it.
• Zero dependencies, no install scripts. Only Node.js built-ins.
• Read-only. It never changes your project.
• Safe on untrusted projects. It never runs project code, and a repository's own git config cannot make the scan run a command.
• Secrets are always masked in every output.
• Verifiable releases. Published with npm provenance from GitHub Actions: npm audit signatures.

Details and vulnerability reporting: SECURITY.md. Wrong or missed finding? Tell us, no code needed.

Expert help

The tool is free and stays free. If your team would rather hand an upgrade over, the maintainer takes on a few projects at a time: send your report to [email protected]. How it works.

License

MIT