The small project has no tests or security policy, and its single maintainer and minimal activity leave little evidence of ongoing support. The clear license, matching repository, and documented release changes help transparency but do not offset the age.
38%
Total Score
38
100
81
50
The latest release was published nearly 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, despite the package having six historical releases.
There were no commits and no active maintainers in the last three months, while the last repository push was nearly 10 years ago. This materially increases abandonment risk.
One registry publishing account is listed for a user-owned project, leaving a thin maintainer base and limited evidence of continuity. No organization backing is shown to compensate for that concentration.
The registry namespace and repository are owned by the same individual account, confirming ownership alignment but not broader project backing. That provides no compensating maintainer capacity for the inactive project.
The repository has one open issue and no new or closed issues or pull requests in the last month. This is consistent with a project that is no longer actively supported.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
php-amqplib/php-amqplib Version 2.6.* | — | — |
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.