Metro configuration for React Native.
88%
Total Score
100
100
85
80
100
The linked repository name does not match the package name and its README does not mention the package, which can make package ownership less transparent. The organization-backed React Native monorepo context partly compensates, but the missing explicit mention remains a caution.
The repository uses Babel, TypeScript, and npm build tooling. No security-scanning tools were detected, leaving a modest security-process gap in an otherwise established build setup.
The repository has no SECURITY.md or other detected security policy. This reduces transparency for reporting vulnerabilities, though the active organization-backed project provides substantial compensating maintenance evidence.
Eleven workflows lack top-level permissions and eight declare top-level write access. Although some workflows are read-only and no untrusted checkout was detected, the broad write-permission profile is a real repository-hardening concern.
Version 0.87.1 is not marked prerelease, but all recent releases are reported in the prerelease-share measure, so the package remains outside a stable major-version line. This is a modest compatibility caveat rather than an abandonment concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
metro-config Version ^0.87.0 | — | — |
metro-runtime Version ^0.87.0 | — | — |
@react-native/js-polyfills Version 0.87.1 | — | — |
@react-native/metro-babel-transformer Version 0.87.1 | — | — |
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.