madnh/laravel-setting

Release historydanger

Only two releases were published, both in December 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the lack of releases and indicating that maintenance has effectively stopped.

Maintainerscaution

Only one registry account has publish access. Because the repository is user-owned rather than organization-backed, this represents a thin publishing and support base.

Repo popularitycaution

The repository has zero stars and forks and one watcher, providing little evidence of community review or support. Popularity is only supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo toolingcaution

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