zbrettonye/hcaptcha

Project backingcaution

The repository is owned by the same individual namespace as the package, providing consistent ownership context. It is a user-owned project rather than organization-backed, so the single-maintainer risk remains relevant.

Release historycaution

The package has six releases but none in about three years, indicating that maintenance has stopped or slowed substantially. Its existing release history provides some maturity, but does not offset the prolonged inactivity.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months, consistent with the multi-year release gap and raising abandonment risk.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no evidence of a broad user or contributor community. Low popularity is supporting caution rather than a verdict by itself.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a minor transparency and maintenance weakness for a package handling CAPTCHA integration.