The MIT license, matching repository, and lack of install scripts improve transparency and reduce installation surprise. The single maintainer and missing security policy leave limited review capacity.
60%
Total Score
50
80
75
Only one registry account has publish access, leaving little visible publishing redundancy. This is a smaller concern because the linked repository is owned by the same individual.
The package includes a README, while the absence of tests and a changelog in the artifact is normal packaging practice. The repository also reports no tests or changelog, limiting project documentation and verification evidence.
The latest release was over two years ago, with no releases in the last 12 months. The repository was pushed more recently, which partly offsets the stale registry cadence but does not show a maintained release stream.
The repository recorded zero commits and zero active maintainers during the last three months. This is a meaningful maintenance warning, although the repository was pushed in July 2025.
The repository has no security policy, so it provides no documented channel or process for reporting vulnerabilities. This is a transparency gap for a package that handles application authorization.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^5.4|^5.5|^7.0|^8.0|^9.0|^10 | — | — |
illuminate/config Version ^5.4|^5.5|^7.0|^8.0|^9.0|^10 | — | — |
illuminate/support Version ^5.4|^5.5|^7.0|^8.0|^9.0|^10 | — | — |
illuminate/database Version ^5.4|^5.5|^7.0|^8.0|^9.0|^10 | — | — |
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.