react-native-inapp-inspector@2.5.19
The zero-config, all-in-one in-app debugger & network logger for React Native & Expo (Flipper, Reactotron & Chucker alternative). Intercept XHR with onloadend support, early pre-mount request queueing, fetch, Axios & GraphQL, inspect console logs with Met
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe server is an intentional developer utility, but its unauthenticated network interface permits remote build-task triggers and APK access once launched. This is a real conditional exposure, so warn rather than block.
Decision evidence
public snapshot- The manifest registers a CLI and an explicit APK-serving script; the CLI starts the standalone server.
- The server listens on 0.0.0.0 and handles build and APK requests without an authentication check.
- The build route accepts a request-supplied Gradle scheme, then starts Gradle in the current project; remote callers can trigger project tasks and retrieve available APKs.
- Both builds attempt to share the exported file through the native helper, then fall back to React Native’s share sheet with the report text and optional file URI.
- The server starts only when a user invokes the package CLI or its APK-serving script, consistent with developer tooling.
Source & flagged code
7 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/esm/metro.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to react-native-inapp-inspector@2.5.19.
See all versions of react-native-inapp-inspector for other recorded verdicts.
- Review the evidence and your use of react-native-inapp-inspector@2.5.19 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.