laravist/geecaptcha

Release historydanger

The package has only two releases, with the latest published in July 2016 and none in the last 12 months. This long release gap materially increases abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push, this is strong evidence that ongoing maintenance has stopped.

Maintainerscaution

Only one account has registry publish access, leaving little visible publishing redundancy. The linked repository is user-owned rather than organization-backed, so the thin maintainer base remains a concern.

Project backingcaution

The repository is owned by an individual account, not an organization, and the registry namespace does not provide evidence of organizational backing. This leaves less visible support capacity for a dormant package.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull request activity. This is consistent with a dormant project, although it does not by itself prove that the package is defective.