Keyboard manager which works in identical way on both iOS and Android
82%
Total Score
healthy
Frequent releases and active repository work support adoption, but unpinned GitHub Actions and a concentrated maintainer base reduce confidence.
A prepare install-time script is present. This adds build-time execution during installation, although no other provided signal indicates that the script is unsafe.
The repository is owned by an individual account rather than an organization, so the concentrated commit activity and single registry maintainer are not offset by visible organizational backing.
One contributor made 40 of 56 recent commits, or about 71%, creating meaningful concentration risk. However, 12 other contributors were active during the same period, partly compensating for that concentration.
The project uses TypeScript, Babel, and npm build tooling, but no security scanning tools were detected. This is a modest repository-hygiene gap rather than evidence of abandonment.
All 118 analyzed action references are unpinned, and the audit found a medium-confidence template-injection finding plus four high-confidence adhoc-package findings. The pull_request_target and workflow_run triggers have no untrusted checkouts or script-injection counts, so these are workflow-hygiene concerns rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react-native-is-edge-to-edge Version ^1.2.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.