The source project has tests, a clear README, and matching MIT licensing, which support basic transparency. Its very small release history and absent recent activity make long-term maintenance uncertain, while workflow hygiene is incomplete.
35%
Total Score
25
80
50
Only two releases were published, both in June 2023, with no releases in the last three years. This is strong evidence of an inactive release process for a library dependency.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long period since the last release. No newer maintenance evidence compensates for this.
There were no new or merged pull requests in the last month, and no issue activity was observed. The unknown open-issue count limits how much can be inferred, but the available activity still suggests low maintenance.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it is a secondary concern compared with the inactive project history.
All three action references are unpinned, and one high-confidence medium-severity finding uses an archived action. The pull_request_target trigger has no untrusted checkout or script-injection sink, so it is not independently dangerous.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version ~3.0.0 | — | — |
hyperf/utils Version ~3.0.0 | — | — |
nesbot/carbon Version ^2.21 | — | — |
psr/container Version ^1.0|^2.0 | — | — |
hyperf/support Version ~3.0.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.