christhompsontldr/laravel-restricted

Release historydanger

Only two releases exist, and the latest was published nearly six years ago with no releases in the last 12 months. This is strong evidence of low maintenance for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long gap since the last release and raising abandonment risk.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a package that adds application middleware.

Version stabilitycaution

The latest version is v0.0.2 rather than a stable major release, indicating limited maturity; there is no recent prerelease churn to offset that concern.