tito10047/iconcaptcha-bundle

Maintainerscaution

Only one registry account can publish releases. The source is user-owned rather than organization-backed, so this leaves a meaningful publishing continuity concern despite two active repository contributors.

Project backingcaution

The repository is owned by the same individual as the registry namespace, with no organization backing shown. This is consistent and transparent, but offers limited institutional maintenance capacity.

Release historycaution

The package is only 30 days old with two releases, spaced about 31 days apart. That shows active initial development but provides little evidence of long-term stability.

Repo toolingcaution

The project uses Composer build tooling, but no security scanning tools were detected. That is a hygiene gap for a package handling authentication-related captcha flows, though it is not evidence of unsafe code.

Security policycaution

The repository has no security policy. This makes vulnerability reporting and response expectations less transparent for a security-sensitive integration.