Connection for communicating with EPP(Extensible Provisioning Protocol) servers via RabbitMQ server
61%
Total Score
50
100
81
83
The registry namespace and repository owner are the same individual, providing direct ownership alignment. The user-owned project has a narrow backing structure, which matters more because recent activity is absent.
The package has six releases over about four years, but no releases in the last 12 months; the last release was about 19 months ago. This indicates materially slowed maintenance for a dependency.
There were no commits and no active maintainers in the last three months. Combined with the long period since the last release, this is evidence of currently inactive development.
Composer is used for the build, which is appropriate, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk for a five-file package.
The linked repository is not archived, but its last push was about 19 months ago, reinforcing the maintenance concern shown by the release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ~1.0 | ~2.0 | ~3.0 | — | — |
symfony/uid Version ~5.0 | ~6.0 | ~7.0 | — | — |
php-amqplib/php-amqplib Version ^3.0 | — | — |
struzik-vladislav/epp-client Version ^2.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.