Clear documentation, licensing, and package identity reduce adoption friction. No security scanning is reported, leaving limited evidence that future issues will be detected and addressed promptly.
58%
Total Score
50
100
88
75
The package and repository are owned by the same individual account. This establishes clear ownership, but it does not provide organizational backing or additional maintenance capacity.
The package has 11 releases, but the latest was published over a year ago and there have been no releases in the last 12 months. This is a meaningful maintenance concern despite the early burst of releases.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release pause. This weakens evidence of ongoing maintenance.
Composer is used for the build, but no security scanning tools are reported. For an authentication-related package, that missing automated security coverage is a genuine hygiene concern.
The repository has no security policy. This reduces transparency about how vulnerabilities should be reported and handled, particularly for a package that controls authentication lockout behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/cache Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/console Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.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.