Usable with caveats: the package is licensed, documented, tested, stable, and not deprecated, but maintenance depends on one contributor and repository activity is very limited. Install it only if you are comfortable owning follow-up maintenance.
68%
Total Score
50
100
83
90
Only one account has registry publish access. That is not evidence of poor maintenance by itself, but it leaves little publishing redundancy for a package owned by an individual.
The package and repository are backed by the same individual account rather than an organization. This is consistent and transparent, but it offers less maintenance redundancy than organization-backed ownership.
Four releases were published during the package's roughly 10-month history, with a median interval of about 3 days. That indicates an initially active release cadence, though the short overall history limits evidence of long-term durability.
All recent commit activity comes from a single contributor, giving the project a bus factor of one. The matching individual registry and repository ownership provides continuity but does not compensate for the lack of a second active maintainer.
Only one commit was made in the last three months by one active maintainer. The recent repository push is reassuring, but the very low activity indicates limited ongoing maintenance capacity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/cache Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/routing Version ^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0|^12.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.