48%
Total Score
unhealthy
Risky: one release, no recent commits, no license, and little documentation leave maintenance and transparency uncertain.
No declared license, license file, or detected repository license was found. That leaves the legal terms for using this dependency unclear.
The published artifact has no README, tests, or changelog; the missing tests and changelog are normal for published artifacts, but the lack of consumer documentation is a real transparency gap for a library.
The package and repository use the matching Verdient namespace, but the repository owner is an individual account rather than an organization. This offers limited backing context without proving a lack of support.
Only one release has been published, about 7 months ago, so there is little release history from which to judge maintenance maturity.
No commits and no active maintainers were recorded during the last three months. For a package with only one release, that is a meaningful warning about ongoing maintenance capacity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/event Version ^3.1 | — | — |
hyperf/config Version ^3.1 | — | — |
hyperf/contract Version ^3.1 | — | — |
hyperf/coroutine Version ^3.1 | — | — |
hyperf/framework Version ^3.1 | — | — |
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.