hyperf-ext/cookie
Documentation, licensing, and repository tests are all present. The release workflow uses two unpinned actions, and the repository has no security policy, adding maintenance and supply-chain hygiene concerns.
57%
Total Score
50
88
50
Health Score Breakdown
The package has had no registry release for more than five years and none in the last 12 months, which is a meaningful sign of stale published maintenance. The repository was pushed in August 2025, so the project is not wholly abandoned.
There were no commits or active maintainers in the last three months, weakening evidence of current development. This is partly offset by the repository's August 2025 push, but the recent activity window remains inactive.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, although it does not by itself indicate abandonment.
The only workflow was fully analyzed with no untrusted checkout or script-injection findings, but both referenced actions are unpinned and one uses an archived action. These are hygiene risks rather than evidence that the release is unfit.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Eric Zhu |
| Taylor Otwell |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 hyperf/di Version ~2.2.0 | — | — |
hyperf/framework Version ~2.2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 6 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.