Testing and documentation are solid, while the package lacks a security policy and uses one unpinned workflow dependency. The MIT license and matching repository provide useful transparency, but the thin maintainer base limits resilience.
46%
Total Score
50
70
50
The package has had only 2 releases, both in February 2020, with no release in roughly 6 years and 7 months. This is strong abandonment evidence, although the repository was pushed more recently.
Only one registry maintainer is listed, so publishing continuity depends on a single person. The repository owner matches that maintainer, which supports attribution but does not provide a broader contributor base.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with a project that is no longer actively maintained. Its more recent historical push prevents this from being conclusive on its own.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters for an authentication guard, even though it does not by itself show abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/auth Version ^5.1|^6 | — | — |
illuminate/http Version ^5.1|^6 | — | — |
firebase/php-jwt Version ^5.0 | — | — |
guzzlehttp/guzzle Version ^6.2.1 | — | — |
illuminate/support Version ^5.1|^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.