The repository is unarchived, has tests, and records three merged pull requests in the last month. Install-time scripts, missing security policy, and broad workflow write permissions leave some maintenance and release-process risk.
70%
Total Score
67
100
88
50
post-install-cmd and post-update-cmd scripts run during Composer operations, adding release and installation complexity compared with a package without lifecycle hooks.
The repository is owned by an individual account rather than an organization, so the single registry maintainer provides limited visible backing capacity.
The package has only four releases since May 2019, with no registry release in about two years and a median interval of roughly 16 months. This is a meaningful cadence concern, although the linked repository shows newer activity.
There were no commits and no active maintainers in the last three months, which weakens evidence of sustained hands-on maintenance. Recent merged pull requests partly offset this concern.
The project uses Make and Composer, but no security scanning tools were detected, leaving a modest repository hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/stream Version ^1.3 | — | — |
react/promise Version ^2.8 || ^3.1 | — | — |
psr/http-message Version ^1.1 || ^2.0 | — | — |
react/event-loop Version ^1.5 | — | — |
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.