Its broad dependency surface and lone registry maintainer increase maintenance risk. The repository could not be found, leaving source activity and provenance unverified.
28%
Total Score
50
50
50
The package explicitly borrows the identity of the much more established laravel/fortify while being owned by someone else. Consumers most likely wanted laravel/fortify, making this a severe adoption risk.
The package declares 26 runtime dependencies, creating a broad maintenance and compatibility surface. No provided signal shows that this complexity is actively managed.
Only one account has registry publish access, leaving a thin visible release-maintenance base. This is a meaningful resilience concern, although registry access alone does not prove who contributes code.
The latest release was about 18 months ago, and there were no releases in the last 12 months. That suggests maintenance may have stopped despite the package being only about 19 months old.
The release is not a prerelease, but the package remains on the 0.1 line, so its compatibility and maturity expectations are limited.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/di Version ~3.1.0 | — | — |
hyperf/config Version ~3.1.0 | — | — |
hyperf/engine Version ^2.1 | — | — |
hyperf/signal Version ~3.1.0 | — | — |
nesbot/carbon Version ^2.72.6 | — | — |
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.