rouxtaccess/laravel-mrmessaging

Release historydanger

The package has made no release in about two years and five months, despite having eight releases overall. This strongly raises abandonment risk for a Laravel integration.

Repo commit activitydanger

There have been no commits and no active maintainers in the last three months, consistent with the last push being about two years and five months ago. This is the clearest evidence of stalled maintenance.

Repo popularitycaution

The repository has zero stars and forks and one watcher, indicating little visible adoption. Popularity is supporting evidence rather than a verdict, but it reinforces the limited maturity signal.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling is configured. This is a modest transparency and hygiene gap, not evidence of unsafe code by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. For a package that handles messaging credentials, this reduces maintenance transparency.