Package Health/xerxes/laravel-rabbitmq-communication

xerxes/laravel-rabbitmq-communication

Usable with caveats: the release is licensed, documented, stable, and backed by a repository with tests and a changelog. However, it has only two releases in about eight months, no commits in the last three months, minimal adoption, and no security policy or scanning.

Latest v2.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months. This is the clearest maintenance concern and suggests current development may have paused.

Project backing

The registry namespace and repository owner are aligned around the same individual account, providing direct ownership continuity, though there is no organization backing to broaden maintenance capacity.

Release history

Only two releases have been published over roughly eight months, with releases about three months apart. That is limited evidence of sustained maintenance for a package handling messaging infrastructure.

Repo popularity

The repository has only three stars and no forks or watchers, indicating very limited independent adoption and correspondingly little visible community support.

Repo tooling

The repository uses Composer but has no detected security-scanning tools. For a package handling message transport and application integration, the absence of automated security checks is a meaningful hygiene gap.