Usable with caveats: it is actively released, documented, licensed, and backed by a maintained repository. The project is young and all recent commits come from one contributor, so long-term continuity depends heavily on a single maintainer.
73%
Total Score
60
100
94
80
Four workflows were analyzed without untrusted checkout or script-injection findings, but one release-drafter workflow uses pull_request_target, which warrants caution in a release-related automation path.
Only one registry account has publish access. This is a continuity concern for a user-owned project, although the linked repository and recent activity show an identifiable active maintainer.
The package and repository are backed by the same individual user rather than an organization, so the single-contributor and single-publisher concerns are not offset by organizational ownership.
One contributor made all six commits in the last three months, creating a meaningful single-maintainer continuity risk with no demonstrated handoff capacity.
There are no open issues or pull requests and no recent issue or pull-request activity. This does not show abandonment by itself, but it provides little independent evidence of community engagement.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version >=10.0 | — | — |
illuminate/support Version >=10.0 | — | — |
illuminate/database Version >=10.0 | — | — |
illuminate/contracts Version >=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.