react-native-inapp-inspector@2.5.17
The zero-config, all-in-one in-app debugger & network logger for React Native & Expo (Flipper / Chucker alternative). Inspect Network (fetch/Axios/GraphQL), Console logs with Metro Symbolication, Redux State, Firebase Analytics, Storage (AsyncStorage/MMKV
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection confirmed an unauthenticated network route that triggers caller-selected Gradle argument processing in the consumer project. The server requires explicit CLI startup, so this supports a warning for a dangerous capability rather than a malicious verdict.
Decision evidence
public snapshot- The package’s APK-serving CLI starts the standalone server when explicitly invoked.
- The build route accepts a `scheme` query value and passes it to the Gradle build helper.
- The helper passes the selected Gradle argument to a subprocess running in the consumer project directory.
- The server binds to all network interfaces, and the reviewed build route has no authentication check.
- The flagged Metro locations resolve to APK paths, build status, and APK serving rather than account actions.
- The network service requires an explicit CLI invocation to start.
- The Gradle process uses an argument array rather than a shell command.
Source & flagged code
8 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.17.
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.17 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.