vkovic/laravel-commando

The MIT license, substantial README, test suite, and absence of install scripts support straightforward use. A single maintainer, no recent issue activity, and no repository security policy or scanning leave less evidence of ongoing care.

Latest v0.2.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by the same individual account that publishes the package. This is consistent ownership, but it does not provide organizational backing to compensate for the thin maintenance base.

Release history

The package has eight releases, but none in the last 12 months and the latest release was about four years ago. That points to a mature but inactive release line.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the release history showing about four years without a new release. This materially raises abandonment risk.

Repo issue activity

The repository has seven open issues and no new or closed issues or pull requests in the last month. Combined with zero recent commits, this suggests limited ongoing maintenance.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This is a transparency and maintenance gap, though it is not severe on its own.