The package has a clear MIT license, tests, a substantial README, and no install-time scripts. Its single-maintainer setup, absent security policy, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
60%
Total Score
63
100
81
75
The latest registry release was February 15, 2023, with no releases in the last 12 months. The 18-release history shows an established package, but the long release gap raises abandonment and compatibility concerns.
One registry account has publish access. Because the repository is user-owned rather than organization-backed, the small maintainer base leaves more bus-factor risk.
The registry namespace and repository owner match, but the owner is an individual rather than an organization, so there is no visible organizational backing to offset the thin maintainer base.
There were no commits and no active maintainers in the last three months. This is a concrete sign of currently limited maintenance capacity, despite the repository having been pushed in March 2025.
Composer build tooling is present, but no security-scanning tooling was detected. For a web access-control package, that is a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/url Version ^1.3 | — | — |
illuminate/console Version ^5.5|^6.0|^7.0|^8.0|^9.0|^10.0 | — | — |
illuminate/support Version ^5.5|^6.0|^7.0|^8.0|^9.0|^10.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.