Organization backing, a matching repository, and a security policy provide useful continuity. The package has only one release, remains a prerelease, and shows no commits or active maintainers in the last three months; unpinned workflow actions add a smaller hygiene concern.
56%
Total Score
50
100
81
83
There were zero commits and zero active maintainers in the last three months, which weakens evidence of ongoing maintenance for a package with only one release.
This package is about six months old but has only one release, so there is little observed release history from which to judge maintenance continuity.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The assessed version is a prerelease, and all recent releases are prereleases, so compatibility and API stability are less established than for a stable release.
Both workflows were analyzed without high- or medium-severity findings, and the pull_request_target workflow has no untrusted checkout or script-injection sink. However, both action references are unpinned, leaving a smaller reproducibility and workflow-integrity concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/event Version ~3.2.0 | — | — |
hyperf/context Version ~3.2.0 | — | — |
hyperf/support Version ~3.2.0 | — | — |
hyperf/database Version ~3.2.0 | — | — |
hyperf/collection 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.