leedom/leedom-captcha

The package has a clear README, matching source repository, MIT licensing, and a small dependency surface. Its only release was over five years ago, with no recent commits or release activity, making abandonment a substantial concern.

Latest v1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over five years ago, with no releases in the last 12 months. That is strong evidence of limited maintenance for a dependency intended for ongoing framework use.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being over five years ago. This materially raises abandonment risk.

Project backing

The repository is owned by an individual user rather than an organization, so the single registry maintainer does not have organizational backing to compensate for the lack of recent activity.

Repo popularity

The repository has one star and no forks, providing little evidence of community adoption or an external support base. Low popularity is supporting caution rather than a verdict by itself.

Repo tooling

The repository uses Composer, which fits the package ecosystem, but it has no security-scanning tools. That is a modest transparency and maintenance gap, not a severe risk on its own.