The package is small and clearly identified, with a focused dependency set, a README, and a stable release. It has had no release or commit activity for over four years, and its single-user project lacks tests and security scanning. That makes ongoing maintenance and timely fixes uncertain.
40%
Total Score
25
100
75
50
Only two releases were published, both in June 2022, with no release in over four years. This is strong evidence of abandonment risk despite the stable current version.
The repository recorded zero commits and zero active maintainers in the last three months, and its last push was in June 2022. The long inactivity materially lowers confidence in ongoing maintenance.
One registry maintainer is consistent with a small user-owned project, but it leaves little visible redundancy for maintenance or security response.
Composer is used for the build, which is appropriate, but no security scanning tooling was detected. That weakens evidence of routine vulnerability detection.
The repository has no security policy, so consumers have no documented channel or process for reporting vulnerabilities. This is a transparency and response gap, though not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-amqplib/php-amqplib Version ^3.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.