verbanent/laravel-sql-performance-guard

Release historydanger

Seven releases were published, but none appeared in the last 12 months; the latest release was about three years and six months ago. This materially raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the stale release history, this is the strongest reason for caution when adopting it.

Repo popularitycaution

The repository has one star, zero forks, and zero watchers, indicating very limited external visibility and little supporting community evidence.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and maintenance gap, though it is not by itself evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.