vectorial1024/laravel-cache-evict

Maintainerscaution

Only one registry account has publish access, which is a resilience concern for an independently maintained package; however, this reflects access configuration rather than actual development activity and is partly offset by the repository and release signals.

Project backingcaution

The repository is owned by the matching Vectorial1024 user account rather than an organization. This is consistent with a personal project but provides less organizational continuity or bus-factor resilience.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers over the last 3 months. This is the clearest maintenance concern, especially because Laravel and related dependencies can require compatibility updates, even though recent release and push signals provide partial compensation.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing security tooling is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

No repository security policy was found. This reduces transparency around vulnerability reporting and response expectations, though it is a caution rather than a standalone severe health risk.