gohany/rtry

Maintainerscaution

Only one registry account has publish access, leaving limited visible publishing redundancy. The linked repository is user-owned rather than organization-owned, so there is no provided evidence of broader organizational backing.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months, while the latest release was about 7 months ago. That quiet period raises abandonment risk despite the earlier releases.

Repo popularitycaution

The repository has zero stars and one fork. This is weak supporting evidence of adoption, but popularity alone does not outweigh the package's documentation and tests.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool is configured. That is a transparency and maintenance-hygiene gap rather than evidence of an unsafe release.

Security policycaution

The repository has no security policy. For a library handling retries around HTTP, RPC, queues, and databases, this weakens the documented process for reporting and handling vulnerabilities.