labidi/recaptcha

Documentation, repository tests, release notes, and a clean workflow audit support adoption. Its single release, one-person ownership, absent security policy, and unpinned actions leave maintenance and build hygiene unproven.

Latest 1.0.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Registry publishing is handled by one individual, and the repository ownership is also an individual account; this gives the project a thin apparent maintainer base.

Project backing

The registry namespace and repository owner match, but both identify an individual rather than an organization, so there is no visible organizational backing to compensate for the thin maintainer base.

Release history

This is the first release, published today, so there is no history showing sustained maintenance or reliable release cadence.

Repo commit activity

There are no commits or active maintainers recorded in the last three months, but the package was released today, so this currently shows an unproven history rather than established abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving an avoidable verification gap for a package handling reCAPTCHA integration.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Saddem Labidi

Direct Dependencies

Dependency	Last Release	Score
illuminate/http Version ^12.40 \|\| ^13.0	—	—
illuminate/view Version ^12.40 \|\| ^13.0	—	—
illuminate/routing Version ^12.40 \|\| ^13.0	—	—
illuminate/support Version ^12.40 \|\| ^13.0	—	—
illuminate/contracts Version ^12.40 \|\| ^13.0	—	—