srcker/captcha

Release historydanger

This release is the package's only release, published about seven years ago, with no releases in the last 12 months. That indicates the project is effectively inactive and increases abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, and its last push was in August 2019. There is no observed recent maintenance capacity.

Maintainerscaution

Only one account has registry publish access. The linked repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops supporting the package.

Repo popularitycaution

The repository has one star and two forks, showing limited adoption and a small apparent user base. Popularity is not required for health, but this provides little supporting evidence of mature maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. This is a modest transparency and maintenance gap for a package that processes user-facing CAPTCHA functionality.