The project has one registry maintainer, no security scanning, and no security policy. Its MIT license, matching repository, clear README, stable version, and modest dependency set provide useful transparency but do not offset the lack of current maintenance.
30%
Total Score
25
100
79
75
The latest release was in December 2015, and there have been no releases in the last 12 months despite the package being over 11 years old. This is strong evidence of abandonment for an authentication library.
The repository recorded zero commits and zero active maintainers in the last 3 months, confirming that the long release gap reflects inactive development rather than registry-only delay.
Only one account has registry publish access. The linked repository is user-owned, so the thin maintainer base provides little evidence of ongoing maintenance capacity.
Composer build tooling is present, but no security scanning tools are configured. For authentication functionality, the absence of automated security checks is a meaningful hygiene gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters for an authentication package and is not compensated by the other provided signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.0 | — | — |
illuminate/contracts Version ~5.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.