sammy-boy/eventbus-core

A single maintainer and no security scanning reduce confidence for a production-facing Laravel library. The MIT declaration, matching repository, and stable v1 release provide useful transparency.

Latest v1.0.2

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed, leaving limited visible publishing redundancy. The linked repository is user-owned, so this is a real capacity concern rather than organization-backed publishing hygiene.

Project backing

The package and repository are owned by the same individual account, confirming an ownership match but offering less organizational backing than a team-owned project.

Release history

All three releases arrived within about 30 minutes on February 6, 2026, and no later release is shown; the latest release is about 7 months old. This suggests an early burst followed by uncertain ongoing maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and the repository has only one open-issue count of zero. Combined with the quiet release history, this provides little evidence of active maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That leaves an avoidable verification gap for a library handling RabbitMQ and Redis-backed event processing.