mennovanhout/laravel-jms

Maintainerscaution

Registry publishing is controlled by one individual, and project backing identifies a personal repository rather than an organization. This leaves limited visible support capacity if the maintainer becomes unavailable.

Release historycaution

The latest release was published nearly four years ago, with no releases in the last 12 months and only three releases overall. This is a meaningful maintenance concern, though the package is not deprecated.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap and increasing abandonment risk.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are present. That reduces verification coverage for a package that is intended to run in application projects.

Security policycaution

The repository has no security policy, so there is no documented path for reporting or coordinating security issues. This is a transparency and maintenance gap, not evidence of malicious behavior.