Package Health/adamtorok96/laravel-settings

adamtorok96/laravel-settings

The release includes tests, a GitHub release note, an MIT declaration, and no install-time scripts. Its single-user project has had no commits or releases since August 2017, with no security policy and no repository evidence clearly tying it to the package name.

Latest 1.1.0

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in 2017, and there have been no releases in roughly nine years. This is strong evidence of abandonment for a Laravel library that may need framework compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in 2017. No newer activity compensates for this prolonged inactivity.

Repo package mention

The repository name does not match the package name, and the collected data shows no README mention of the package. A subpackage mismatch can be normal, but without a confirming mention the package-to-repository link is less transparent.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful community backing to offset the lack of maintenance.

Security policy

The repository has no security policy. This is a transparency and response-process gap, though it is less severe than the long maintenance gap.