The last release was over five years ago, and the repository has had no recent commits or issue activity. Clear licensing, release notes, tests, and an unarchived project provide useful transparency, but missing security guidance and unpinned workflow actions add maintenance risk.
55%
Total Score
25
100
79
83
The repository recorded zero commits and zero active maintainers in the measured three-month period. This is the strongest evidence that active maintenance has stopped.
The latest release was in February 2021, with no releases in the preceding 12 months of the scan period. This long release gap materially raises abandonment risk despite a history of nine releases.
There were no new or closed issues and no pull-request activity in the measured month, while three issues remain open. Together with the old last release, this supports a maintenance concern.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of an unsafe package.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear, adding a modest transparency concern for a networking library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/socket Version ^1.0 || ^0.8 || ^0.7 | — | — |
react/stream Version ^1.0 || ^0.7 || ^0.6 || ^0.5 || ^0.4.6 | — | — |
react/promise Version ~2.0|~1.1 | — | — |
clue/qdatastream Version ^0.8 | — | — |
react/event-loop Version ^1.0 || ^0.5 || ^0.4 || ^0.3 | — | — |
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.