sofwar/laravel-rabbitmq

The MIT license, tests, release notes, and matching repository improve transparency. No security policy or automated security scanning leaves the project’s maintenance hygiene thinner.

Latest v0.5.2

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package’s only release, published about 16 months ago, with no releases in the last 12 months. That limited history makes ongoing maintenance uncertain.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last three months, consistent with the long gap since its last release. This is a meaningful abandonment concern.

Repo popularity

The repository has zero stars, forks, and watchers, offering no supporting evidence of broad community review or adoption. Popularity is only supporting evidence, so this modestly lowers confidence rather than determining the verdict.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities. This is a modest transparency and maintenance gap.