kyzegs/guzzle-rate-limit-middleware

Repo bus factorcaution

All three recent commits came from one contributor, giving the project a single-person maintenance dependency. The repository is user-owned rather than organization-backed, so there is no shown handoff capacity to offset that concentration.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap, though it is not by itself evidence that the release is unsafe.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This lowers project transparency but is not a severe dependency risk on its own.