Usable with caveats: the package has a six-year release history, recent releases, active repository backing, and tests, but only one recent contributor and no package README leave maintenance resilience and consumer documentation weaker.
72%
Total Score
67
88
67
One of two workflows uses pull_request_target, which can increase CI risk, but no untrusted checkout or script-injection patterns were detected. The mitigations keep this at caution rather than danger.
The package artifact has no README, which makes integration harder for a library, but the repository contains tests and this exact version has GitHub release notes. The missing package tests and changelog are normal for published artifacts.
All 2 recent commits came from one contributor, giving the project a concentrated recent maintenance base. Organization ownership provides some handoff capacity, but no second recent contributor is shown.
Only 2 commits were recorded in the last 3 months, showing limited recent development activity despite the recent release. This is a modest maintenance concern rather than evidence of abandonment.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a transparency gap, though it is not by itself evidence of unsafe maintenance.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version ~3.2.0 | — | — |
hyperf/codec Version ~3.2.0 | — | — |
hyperf/engine Version ^2.0 | — | — |
hyperf/command Version ~3.2.0 | — | — |
hyperf/support Version ~3.2.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.