Is React code finder safe?
React code finder stores React component props from inspected sites and can send editor selections to localhost.
React code finder injects into all HTTP and HTTPS pages, and when inspection is enabled it reads React component source metadata and pending props, then stores current and temporary debug selections in Chrome local storage. Its page message bridge also accepts a hardcoded marker from web pages, so while the DevTools panel is open those stored selections can drive localhost editor-helper requests with file, line, and column parameters.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itunqocn - no other listings under this identity
unqocn - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 2.2.9. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Store data in your browser
storage
Where it sends data
Destinations our analysis observed React code finder contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- localhost:3010
React code finder sends data to localhost:3010. Named as a recipient by 1 other extensions we have analysed.