The README, MIT license, repository tests, and exact GitHub project make adoption straightforward. Unpinned CI actions and no security policy reduce transparency, while the single registry maintainer leaves limited visible support if framework compatibility changes.
56%
Total Score
50
100
93
50
Only one account has registry publish access. This is a limited visible publishing base for a user-owned project, though registry access alone does not prove how many people maintain the source.
The package has 14 releases over more than 11 years, but none in the last four years; the latest registry release was in June 2022. This is a substantial maintenance concern, although the stable release and non-archived repository provide some compensation.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push nearly four years ago. The project is not archived, but the absence of recent activity materially increases abandonment risk.
The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is not evidence of a vulnerability by itself.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings, but all three action references are unpinned. The missing top-level permissions block is acceptable on its own, while unpinned actions remain a supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0 | — | — |
illuminate/support Version ^9.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.