The repository has tests, release notes, and a clear README, while its organization backing and matching source reduce identity concerns. Unpinned workflow actions and no security policy add smaller maintenance and supply-chain gaps.
58%
Total Score
63
79
75
There were zero commits and zero active maintainers in the past three months, despite the repository having been pushed around the latest release. This is the strongest evidence of possible maintenance stagnation.
The package is young at 247 days old and has two releases, with a median interval of about 5 days. That shows an initial release effort but provides limited evidence of sustained maintenance.
There were no new or closed issues or pull requests in the past month, and no open issues or pull requests. This may reflect a small or quiet project, but it offers little evidence of current community activity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of unsafe code.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package intended to handle WebSocket connections.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
react/async Version ^4.3 | — | — |
ratchet/pawl Version ^0.4.1 | — | — |
react/promise Version ^3.2 | — | — |
react/event-loop Version ^1.5 | — | — |
react/promise-timer Version ^1.11 | — | — |
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.