caseyamcl/guzzle_retry_middleware

Project backingcaution

The registry namespace and repository are owned by the same individual rather than an organization. This is consistent ownership, but it provides less organizational continuity than an organization-backed project.

Repo toolingcaution

The project uses Composer for builds, but no security scanning tools were detected. For a small library this is a hygiene gap, not evidence of abandonment or an unsafe release by itself.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency, although recent commits, tests, and release notes provide other maintenance evidence.

Workflow auditcaution

The sole workflow was fully analyzed with no untrusted checkouts, script injection, or audit findings, and it has no broad top-level write permission. However, all three action references are unpinned, leaving avoidable build-reproducibility and action-substitution risk.