4 findingsStatic scanned
Puts Claude in your terminal to understand your codebase, edit files and handle git workflows.
80.2M installs/moSEE LICENSE IN README.md
React Native Debug Toolkit
superzcjjj · App
React Native Debug Toolkit helps you follow a failure in a React Native app from the action to the evidence behind it. An in-app inspector shows requests and console output after setup, plus state changes once you add a small integration. A local hub on your computer gathers device sessions to search in a browser, and a read-only command line gives your AI coding assistant the same runtime evidence. It needs no account or cloud log service. It is meant for debug and internal builds, and logs are not redacted automatically.
Written by ooruby from the README of react-native-debug-toolkit 4.1.2.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
A bug seen on a phone comes with its requests, logs and state on your computer, so you or your AI assistant can work from evidence.
What you could do with it
- Reproduce a failed checkout on a device, then ask your AI assistant to find the cause from the runtime logs.
- Open the local browser console to search logs and expand request details while you operate the app.
- Check a failing request's status and JSON response in the floating inspector while you reproduce the problem.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (node/hub/src/cli/commands/hubStart.js:5)
- node child_process (node/hub/src/cli/commands/initSkill.js:6)
- synchronous shell execution (node/hub/src/cli/commands/initSkill.js:232)
- node child_process (node/hub/evals/runtime-diagnostics/cliBroker.js:7)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
AI-first local runtime log Hub for React Native — debug with CLI and Web Console
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 4.1.2, the file with digest sha512-/AsNj6ur5VEFcemoKL8dxTD0+NtosaK+/3ArJDnds+nfXVjxTZFsE+DkLs0cdrZb2RjGUPSQ/POXXXBN2Zafig==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y react-native-debug-toolkit@4.1.2Pinned to 4.1.2, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- react-native-debug-toolkit
- Version read
- 4.1.2
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/react-native-debug-toolkit)About this listing
- Kind
- App
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-06
Similar apps
All appsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.