lain/laravel-operator

Release historydanger

Only two releases were published, both in December 2022, and there have been no releases for nearly four years. This strongly reduces confidence in ongoing maintenance, despite the package not being deprecated.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The repository is not archived, but there is no observed recent maintenance activity.

Maintainerscaution

Only one registry maintainer is listed, which creates a thin support and continuity base for an independently owned package. This is partly consistent with the small project size but still increases abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That limits evidence of ongoing supply-chain hygiene without making the package unfit by itself.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear. This is a transparency gap, though it is less serious than the lack of maintenance activity.