mjpakzad/laravel-settings

Release historydanger

This package has had only one release, with no releases in nearly four years. That strongly suggests the project may be abandoned, although the repository is not archived.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap and limited maintenance capacity.

Maintainerscaution

One registry maintainer is workable for a small package, but it creates a thin support base when combined with the absence of recent commits and releases.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That reduces evidence that dependency or code risks are being checked proactively.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package used in application infrastructure.