kyleleber/google_recaptcha_v3

Release historydanger

The package has only three releases, all concentrated around June 2019, with no releases in the last 12 months and about seven years since its first release. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2019. This substantially raises maintenance risk.

Licensecaution

No license is declared, and neither the package nor the linked repository contains a recognized license file. This creates a material adoption and redistribution concern.

Maintainerscaution

One individual has registry publish access, with no organization backing shown. A single maintainer is not inherently unhealthy, but here it provides little redundancy alongside the long inactivity period.

Repo package mentioncaution

The repository name matches the package, which supports the link, but the README does not mention the package name. This leaves a small ownership and packaging-transparency gap.