rabbit/amqp

The MIT license, Composer build setup, and organization-owned repository provide a clear legal and source baseline. A single publisher, no tests or security policy, and limited repository support make long-term maintenance harder to trust.

Latest 1.0.0

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about 6 years ago, with no releases in the last 12 months. That sparse history is strong evidence of limited ongoing maintenance.

Repo commit activity

The repository had 0 commits and 0 active maintainers during the last 3 months. Combined with the old last push, this indicates substantially reduced maintenance capacity.

Maintainers

Only one registry account has publish access, which creates a narrow publishing base. The organization-backed repository partly offsets this, but does not demonstrate active maintenance.

Package scaffolding

The exact release has release notes stating “first release,” which documents its changes. The missing README reduces consumer guidance, while absent tests and changelog are normal for a published artifact and are not concerns here.

Repo popularity

The repository has 0 stars and 0 forks, with 1 watcher. Popularity is only supporting evidence, but these counts provide little external indication of adoption or review.