blueways/bw-captcha

A clear README, tests, frequent releases, and an exact repository match improve day-to-day confidence. Licensing and release notes are also in place, but no security policy and one-person activity leave limited backup.

Latest 5.4.1

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository owner is an individual account, not an organization, so the single-contributor maintenance pattern is not visibly backed by a broader team.

Repo bus factor

All recent commits came from one contributor, with a 100% top-contributor share. The repository owner is an individual rather than an organization, so there is little visible handoff capacity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. That is a maintenance and transparency gap, though not evidence of an unsafe release by itself.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities.

Workflow audit

All four workflows were analyzed successfully and no audit findings or untrusted checkout/script-injection sinks were reported. However, all 12 action references are unpinned, which weakens build reproducibility; the pull_request_target trigger has no identified dangerous sink.