vvvkor/laravel-cms-base

Release historydanger

The latest release was in June 2018, with no releases in the last 12 months; the package has been without a release for about 8 years. This is strong evidence of abandonment despite six historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, with the last push in October 2018. That sustained lack of development materially increases abandonment risk.

Maintainerscaution

The registry lists one maintainer, which creates a thin publishing base. The linked repository is owned by the same individual, so this is consistent ownership but offers little redundancy if that maintainer stops work.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, and no open issues or pull requests. With the old release and commit history, this supports a conclusion of inactivity rather than active stability.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.