A single maintainer and no published security policy leave limited fallback if problems arise. The matching repository, tests, release notes, and MIT license provide useful transparency.
68%
Total Score
50
100
100
50
Only one registry account has publish access, leaving little publishing redundancy. Because the project is user-owned rather than organization-backed, this is a meaningful resilience concern.
The repository recorded no commits and no active maintainers in the last three months, indicating a recent pause in development despite the latest release and later repository push.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled. The repository does include Dependabot scanning, which provides some compensating security tooling.
All four analyzed workflow action references are unpinned, which weakens build reproducibility. The audit found no dangerous triggers, untrusted checkouts, script injection, or other reported findings, so this is a hygiene concern rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^12.40.2|^13.0 | — | — |
illuminate/database Version ^12.40.2|^13.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.