The repository has only two commits in three months, all from one contributor. A missing security policy and two unpinned workflow actions add modest transparency and build-risk concerns, while recent release notes and passing tests help.
68%
Total Score
67
93
75
The package has only 3 releases across about 8 years, with 1 release in the last 12 months; the latest release is recent, but the long median interval signals slow maintenance.
One contributor made all two recent commits, leaving maintenance dependent on a single active individual even though the repository is organization-owned.
Two commits were made in the last three months, showing recent work, but the volume is limited and supports the maintenance concern seen in the contributor concentration.
The repository has no security policy, reducing transparency about how vulnerability reports are handled; this is a gap, not evidence of unsafe code.
The single workflow is fully analyzed, uses read-only permissions, and has no reported audit findings, but both action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^5.5 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/database Version ^5.5 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^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.