Documentation, tests, licensing, and release notes are solid. The project is less than one day old, has no observed commit history yet, and all six workflow actions are unpinned, so long-term maintenance and build reproducibility remain uncertain.
62%
Total Score
50
100
86
75
The repository is owned by an individual account rather than an organization. This is not inherently unhealthy, but it provides less visible organizational backing for a package with only one registry maintainer.
This package is less than one day old with only two releases, published about 22 minutes apart. That is too little history to demonstrate sustained maintenance, although the short age also explains the lack of longer-term activity evidence.
No commits or active maintainers were observed in the last three months. Because the package is less than one day old, this is mainly an evidence gap rather than proof of abandonment.
The repository uses Composer and Make, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not a standalone adoption blocker.
The repository has no security policy. That weakens vulnerability-reporting transparency for a package intended to be used in applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^3.8 | — | — |
illuminate/support Version ^12.0|^13.0 | — | — |
illuminate/contracts Version ^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16.2 | — | — |
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.