elzdave/benevolent

Maintainerscaution

One registry account has publish access. The repository is user-owned rather than organization-backed, so there is little visible maintainer redundancy if the owner becomes unavailable.

Release historycaution

The latest release was published in August 2023, with no releases in the following 12 months; at assessment time, this is over three years without a release. That materially raises abandonment risk for a Laravel integration package.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is strong evidence that active maintenance has stopped.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap alongside the inactive maintenance signals.

Security policycaution

The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, though it is not evidence of a vulnerability by itself.