elcodedocle/captchalot

The repository has had no commits in roughly two years, and it has no security scanning or policy. Clear licensing, documentation, a matching repository, and a release note provide useful transparency.

Latest 1.2.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by the matching individual registry namespace, providing consistent ownership context. It is user-backed rather than organization-backed, so the available maintainer capacity is limited.

Release history

The package has six releases, but none in the 12 months before collection; its latest release was about two years ago. This indicates slow or stopped maintenance for a service package.

Repo commit activity

There were no commits and no active maintainers in the three months before collection, consistent with roughly two years since the last repository update. This is a meaningful abandonment concern.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project, but the absence of backlog is not itself a maintenance guarantee.

Repo popularity

The repository has one star and no forks, indicating little community validation or visible external support. Popularity is supporting evidence, so this modestly lowers confidence in long-term resilience.