think.studio/laravel-release-protection

Release historydanger

The package has only two releases, both published about three years ago, with no releases in the last 12 months. That long period without a new release is a meaningful abandonment concern.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long release silence. No provided activity signal compensates for this gap.

Licensecaution

The artifact includes a license file, but the manifest declares MIT while the detected text is MIT-0. The package is licensed, yet the mismatch reduces transparency and should be resolved before adoption.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher, so there is little visible community adoption or review capacity. Popularity is supporting evidence rather than decisive on its own.

Security policycaution

The linked repository has no security policy. This is a transparency and maintenance gap, although the absence is not by itself evidence that the package is unsafe.