The project has had no commits or active maintainers for about 11 months, and its release history is still small. Tests, documentation, organizational backing, and a matching repository provide useful support, but workflow references are unpinned.
62%
Total Score
75
86
50
Only two releases exist, with one release in the last 12 months and a median interval of about 59 days; this is a small but not inherently unhealthy history.
There were zero commits and zero active maintainers in the last three months, indicating maintenance has been inactive for about 11 months since the latest push.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository-hygiene gap.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities in a package with database and authorization features.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but both of its two action references are unpinned, weakening reproducibility and update control.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
litepie/tenancy Version ^1.0 | — | — |
illuminate/events Version ^12.0 | — | — |
illuminate/support Version ^12.0 | — | — |
illuminate/database Version ^12.0 | — | — |
illuminate/validation Version ^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.