hyperf/di
Healthy and suitable to depend on, with strong release history, active organizational backing, and a current non-archived repository. Review the permissive GitHub workflow settings and note that recent repository activity is light, though two maintainers remain active and releases are frequent.
82%
Total Score
88
100
94
80
Health Score Breakdown
One of two workflows uses pull_request_target, which requires careful trust-boundary handling, but no untrusted checkout or script-injection patterns were detected.
Only 2 commits were made in the last 3 months, indicating light recent development, but two maintainers were active and the registry shows 11 releases in the last year.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest transparency and preventive-maintenance gap.
Neither workflow declares top-level token permissions, so the repository does not visibly enforce least privilege even though no workflow requests explicit top-level write access.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/stdlib Version ~3.2.0 | — | — |
psr/container Version ^1.0 || ^2.0 | — | — |
hyperf/context Version ~3.2.0 | — | — |
hyperf/support Version ~3.2.0 | — | — |
symfony/finder Version ^6.0 || ^7.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 7 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.