An annotation declaration that adapts to the hyperf framework to cover dependency relationships
43%
Total Score
50
100
83
75
Only two releases exist, and there have been no releases in the last 12 months; the latest release was about two years ago. This is meaningful abandonment risk for a dependency.
The repository had zero commits and zero active maintainers in the last three months, providing no evidence of ongoing maintenance capacity.
The repository has 1 star and no forks, indicating a very small user and contributor footprint. Popularity is only supporting evidence, but it provides little external resilience against abandonment.
Composer is used as the build tool, but no security-scanning tooling is present. The missing scanner is a modest hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and response-readiness gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version ^3.1 | — | — |
hyperf/event 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.