Its MIT license, substantial README, repository tests, and stable release make the package understandable to integrate. The release workflow also has avoidable dependency-pinning and security-hygiene weaknesses.
42%
Total Score
50
50
88
50
The package declares 15 runtime dependencies, including the framework and mailer stack it integrates with. This is a relatively broad dependency surface, increasing maintenance exposure for an inactive package.
The repository is owned by an individual account rather than an organization, so there is no shown organizational backing to compensate for the inactive commit history.
The package has had no release in more than four years: its latest release was May 5, 2022, despite a six-release history. This strongly raises abandonment risk for a mail integration library.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the last push more than four years ago, this indicates that fixes and compatibility updates are unlikely.
The repository uses Composer, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap, especially for a package with a broad runtime dependency surface.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version ~3.0.0 | — | — |
hyperf/view Version ~3.0.0 | — | — |
hyperf/event Version ~3.0.0 | — | — |
hyperf/config Version ~3.0.0 | — | — |
hyperf/command 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.