lemberg/laravel-project

The MIT license, tests, README, and release notes make the template easier to inspect and adopt. Its repository is not archived and the package is not deprecated, but those positives do not offset the thin maintenance record for a production dependency.

Latest 5.5.0

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over eight years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the measured month. Combined with the single-release history, this provides no evidence of an active maintenance channel.

Repo popularity

The repository has zero stars and zero forks, providing little supporting evidence of community adoption. Popularity is only secondary evidence, so this modestly reinforces the maintenance concern rather than deciding it.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling was detected. This is a hygiene gap, not a severe risk, and it adds only modest concern alongside the stale maintenance record.

Security policy

The repository has no security policy, reducing transparency about vulnerability reporting and response. This matters more for a framework-based project but remains secondary to the lack of recent maintenance.