efureev/laravel-support-db

Maintainerscaution

Only one registry account has publish access. Because the repository is user-owned rather than organization-backed, this leaves a relatively thin publishing base, although release history shows the account has been active.

Repo commit activitycaution

The repository records 0 commits and 0 active maintainers in the last three months, which is a meaningful maintenance concern despite a recent push and frequent registry releases.

Repo popularitycaution

The repository has only 3 stars, 0 forks, and 1 watcher. Low adoption is supporting caution rather than a decisive health problem, since other signals show sustained releases and repository structure.

Security policycaution

The repository has no security policy. This is a transparency gap for reporting vulnerabilities, though it does not by itself indicate abandonment.

Token permissionscaution

One workflow lacks top-level permissions and another grants top-level write access, leaving workflow privileges less tightly constrained than ideal. This is a workflow-hygiene concern, not a health verdict on the package itself.