The compat-data to determine required Babel plugins
91%
Total Score
100
100
90
80
100
Two of 13 workflows use pull_request_target, which warrants scrutiny because that trigger can expose privileged workflow context, but no untrusted checkout or script-injection patterns were detected.
The linked repository name does not match the package name and its README does not mention @babel/compat-data, creating some uncertainty about direct package-to-repository linkage; the matching @babel namespace and Babel monorepo context partially mitigate this concern.
The repository uses multiple build tools and has an established build system, but no security-scanning tools were detected, leaving a modest security-process hygiene gap.
Most workflows declare read-only permissions, but two lack top-level permissions and one has top-level write access, leaving some permission-hardening gaps.
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.