butik/rabbitevents

Release historydanger

The package has made five releases since November 2018, but none in the last 12 months; the latest release was in October 2019, nearly seven years ago. This is strong evidence of abandonment risk despite the earlier release cadence.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.

Dependency profilecaution

The package declares 11 runtime dependencies, including several Laravel components and RabbitMQ transport libraries. This is a meaningful compatibility surface for an unmaintained integration, increasing the cost of ecosystem changes.

Repo popularitycaution

The repository has zero stars and forks and only two watchers, so there is little visible community support to compensate for the lack of recent maintainer activity.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tooling is present. This is a hygiene gap rather than a standalone dependency blocker, though it provides little additional assurance for an old package.