mll-lab/laravel-comment

Healthy and reasonable to depend on, with a small maintenance caveat. It has a long release history, a recent stable release with release notes, matching organization-backed source, tests, and no deprecation or archived repository; recent work is limited to one contributor and the project lacks a security policy.

Latest 2.0.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All two recent commits came from one contributor, creating a narrow recent maintenance base. Organization backing provides some ability to hand off maintenance, but no second recent contributor is shown.

Repo commit activity

The repository had two commits in the last three months, so it is not abandoned, but all recent activity came from only one active maintainer.

Repo popularity

The repository has six stars and four forks, showing limited adoption. This is supporting evidence rather than a decisive health problem because the package has a long history and current release activity.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. This is a transparency gap, though the repository's other validation and workflow evidence partly offsets it.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but does not by itself indicate abandonment or unsafe code.