Clear licensing, documentation, and package-repository alignment support adoption. No security policy and the aging Laravel scaffolding leave compatibility and maintenance uncertain.
45%
Total Score
33
100
88
83
The latest release was about 4 years 6 months ago, with no releases in the last 12 months. That long gap materially raises abandonment and compatibility risk despite a stable release history.
There were zero commits and zero active maintainers in the last 3 months, with the last repository push about 4 years 6 months ago. This is strong evidence of inactive maintenance.
The repository is owned by a user account rather than an organization, so the small registry maintainer list does not benefit from identifiable organizational backing.
There were no new or closed issues or pull requests in the last month. With no recent commits, this indicates little current project activity rather than an actively maintained quiet project.
The repository has no security policy. For an authentication and scaffolding package, that reduces transparency around vulnerability reporting and maintenance responsibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/fortify Version ^1.11 | — | — |
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.