Documentation and packaging are straightforward, with a clear license, release notes, and repository tests. The small project footprint, pre-1.0 status, long release gap, missing security policy, and unpinned workflow actions limit confidence for long-lived production use.
55%
Total Score
75
100
75
83
Only three releases have been published, with no release in the last 12 months and a long median interval between releases. This points to limited maintenance activity, though the latest release is present and not withdrawn.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This is a material maintenance and abandonment concern.
The repository has four stars, no forks, and no watchers, indicating a small user and contributor footprint. Popularity is supporting evidence rather than a verdict, but it offers little evidence of broad community support.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency for a package intended to handle server-sent events.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/http Version ^1.9 | — | — |
react/stream Version ^1.3 | — | — |
react/event-loop Version ^1.4 | — | — |
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.