muhammadshakeel/laravel-api-boilerplate-oauth

Release historydanger

The package has had no release in more than 10 years, with zero releases in the last 12 months. This is strong evidence of abandonment for a framework starter package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release silence. No provided maintenance signal offsets this.

Lifecycle scriptscaution

The package defines post-install, post-update, and pre-update Composer scripts. These can be legitimate setup behavior, but they increase install-time execution surface without other evidence showing how those scripts are maintained.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, and no open work is visible. Combined with the stale release history, this supports a lack of ongoing maintenance.

Repo toolingcaution

Composer is used for builds, but no security-scanning tool is present. That is a meaningful hygiene gap for a package handling authentication and OAuth2 configuration.