The package includes tests, a README, and a clean nine-file artifact, while its single CI workflow has no dangerous patterns. It lacks security scanning and explicit workflow token permissions, so ongoing maintenance and CI hardening remain limited.
55%
Total Score
75
80
75
The latest release was nearly five years ago, with no releases in the past 12 months. That is a substantial maintenance concern for a dependency, despite the package having ten releases over its lifetime.
The repository recorded no commits and no active maintainers in the past three months, consistent with prolonged inactivity. The repository is not archived, but that does not offset the lack of recent work.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces maintenance and security-process confidence without making the release unfit on its own.
The repository has no security policy. For a small package this is a transparency gap, though it is less serious than abandonment because the source, tests, and ownership are visible.
The sole workflow has no top-level token permissions declaration. No write permissions or dangerous workflow patterns were found, but explicit least-privilege configuration would provide stronger CI hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/event-loop Version ^1.0 || ^0.5 || ^0.4.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.