Usable with caveats: it has recent releases, a working repository, tests, documentation, and organizational backing. Recent source commits are absent despite two merged pull requests, and the project has no security policy or scanning, so ongoing maintenance and security transparency deserve attention.
68%
Total Score
83
89
90
There were no commits and no active maintainers in the last 3 months, which is a real maintenance concern. However, two pull requests were merged in the last month, and the recent release and push provide partial evidence of continued activity.
The repository has 10 stars, 2 forks, and 1 watcher, indicating a small user and contributor footprint. This is supporting caution rather than a severe risk because the package shows releases, tests, and organizational backing.
Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces security-process transparency without demonstrating that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a service-discovery component, though it is not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
teamones/log Version >=0.0.1 | — | — |
ark/filecache Version ^0.1.0 | — | — |
teamones/http Version ^0.0.4 | — | — |
illuminate/redis Version ~8.20 | — | — |
teamones/json-rpc Version >=0.0.1 | — | — |
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.