The MIT license, README, repository tests, and release notes provide useful transparency. There is no security policy or automated security scanning, and the project has no established commit history yet.
58%
Total Score
50
100
86
88
The package is less than 1 day old with only 2 releases, about 19 minutes apart, so there is not enough history to demonstrate sustained maintenance.
There were 0 commits and 0 active maintainers in the last 3 months. Given that the project is less than 1 day old, this shows no established maintenance record rather than a proven collapse, but it still limits confidence.
Composer build tooling is present, but no security scanning tools are configured. This is a transparency and maintenance gap, not evidence that the release is unsafe by itself.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.9 | — | — |
amphp/websocket-client Version ^2.0 | — | — |
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.