Tests, a substantial README, and matching MIT licensing provide useful support for adoption. The release workflow has unpinned actions and uses an archived action, adding avoidable maintenance risk.
42%
Total Score
0
67
50
Only two releases were published, both in July 2021, with no releases in the last 12 months and an effectively five-year-old release history. That is strong evidence of abandonment for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
The repository has no security policy or security scanning tools. For an old, inactive package this reduces transparency and vulnerability-reporting support, though it is less important than the demonstrated maintenance gap.
The workflow audit completed fully and found no untrusted checkout or script-injection paths, but both referenced actions are unpinned and one uses an archived action. This is a hygiene and maintenance concern, not a standalone critical risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version 2.2.* | — | — |
hyperf/view Version 2.2.* | — | — |
hyperf/event Version 2.2.* | — | — |
hyperf/config Version 2.2.* | — | — |
hyperf/command Version 2.2.* | — | — |
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.