Apex reliability suite (RateLimit, Idempotency, Outbox, Notify, Outbound) for Hyperf
58%
Total Score
caution
Only two days old, with four commits from one contributor and no security policy.
The repository owner is a user account, not an organization, so there is no demonstrated organizational maintenance capacity to offset the concentrated contributor base.
The package is only 2 days old with 5 releases, and its median release interval is about 3 hours 16 minutes. This shows active initial development but provides too little history to establish dependable maintenance.
One contributor made 100% of the 4 recent commits. With the repository owned by a user rather than an organization, this creates a meaningful single-maintainer continuity risk.
There were 4 commits in the last 3 months, all within this newly created package's short lifetime. Activity exists, but there is not yet enough sustained history to support a strong maintenance assessment.
Composer is used for builds, but no security-scanning tools were detected. The absence of automated security tooling weakens repository hygiene, though it is not evidence of a defect by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/redis Version ~3.2.0 | — | — |
hyperf/guzzle Version ~3.2.0 | — | — |
hyperf/database Version ~3.2.0 | — | — |
hyperf-apex/core Version ^4.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.