The repository is small but has tests, a clear README, an MIT license, and organization backing. Its early release burst, three-month commit gap, and workflow weaknesses leave limited evidence of sustained maintenance.
57%
Total Score
75
75
50
Five releases arrived within a very short initial burst, but the latest release was about 4 months and 3 weeks ago, so the history shows limited sustained maintenance.
The repository recorded zero commits and zero active maintainers over the last 3 months, leaving a meaningful abandonment concern despite its recent launch.
The linked repository has no security policy, reducing transparency about how users should report vulnerabilities; this is a hygiene gap rather than evidence of an unsafe release.
Version v0.1.4 is not a stable major release, which signals an immature API and greater compatibility risk for dependents.
All 12 action references are unpinned, three workflows grant top-level write permissions, and a high-confidence bot-conditions finding affects the Dependabot auto-merge workflow. The pull_request_target trigger has no untrusted checkout or script-injection sink, so this remains a caution rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.