Its long release history, stable versioning, tests, and organization-backed repository support confidence. The license mismatch and unpinned workflow actions add hygiene concerns alongside the recent maintenance lull.
62%
Total Score
83
100
89
67
The artifact declares Apache-2.0 but its LICENSE file is detected as MIT, creating an unclear licensing position despite license files being present in both the artifact and repository.
The package defines four install and update lifecycle scripts. These warrant attention because they execute package logic during Composer operations, but the signal alone does not establish a health failure.
The repository recorded zero commits and zero active maintainers in the past three months, a meaningful sign of a recent maintenance lull despite the recent release history.
The project uses Composer, but no security scanning tools were detected. This is a transparency and hygiene gap, not evidence that the release is unsafe.
Both workflows were analyzed with no untrusted checkout or script-injection paths, but all 3 action references are unpinned and a high-confidence medium-severity archived action was found in the release workflow.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/cache Version ~3.2.0 | — | — |
hyperf/config Version ~3.2.0 | — | — |
hyperf/engine Version ^2.10 | — | — |
hyperf/guzzle Version ~3.2.0 | — | — |
hyperf/logger 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.