Debugger frontend for React Native based on Chrome DevTools
78%
Total Score
100
79
67
100
The linked repository neither matches the package name nor mentions it in its README. The package README points instead to a separate react-native-devtools-frontend source repository, so the collected repository does not clearly establish the package's source.
The project uses Babel, TypeScript, and npm scripts, showing an established build setup. No security-scanning tools were detected, which is a modest process gap.
No repository security policy was found. This weakens disclosure transparency, although the active organization-backed project provides some compensation.
Version 0.87.1 is not a stable major release, and all recent releases are prereleases by the indicator. This adds some API-stability uncertainty despite the active release cadence.
The audit found 122 unpinned action references out of 133, several high-confidence template-injection findings, wide permissions in 8 workflows, and secrets inheritance; however, there were no untrusted checkouts or script-injection findings. Five of 35 workflows were not analyzed, so workflow hygiene remains a real caution rather than a release-blocking danger.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.