keljtanoski/modular-laravel

Release historydanger

The package has 40 releases and historically released about every 9 days, but it has had no release in over three years and none in the last 12 months. That long gap is a substantial abandonment concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, while the latest push was over three years ago. This is the strongest evidence that ongoing maintenance has stopped.

Lifecycle scriptscaution

Several Composer lifecycle scripts run during installation and project creation, which increases execution complexity for a package intended to create Laravel applications. This is expected for its blueprint role but still warrants review before automated adoption.

Project backingcaution

The registry namespace and repository owner match, which supports ownership consistency. The owner is an individual, so there is no organizational backing signal to compensate for the thin maintenance evidence.

Repo issue activitycaution

There are seven open issues but no new or closed issues and no pull requests in the last month. That suggests unresolved maintenance needs and no visible recent project response.