The README is detailed, tests are present, and the runtime dependency set is small. Maintenance evidence is limited after an initial burst, while the repository has no security policy and no visible community activity.
58%
Total Score
75
83
50
There are only two releases, both published within about 14 minutes on the same day, followed by about four months without another release. This is limited evidence of an established release process.
The repository has no commits and no active maintainers in the last three months. For a package released only about four months ago, this is a meaningful maintenance concern.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no external adoption signal for the otherwise young project.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not a severe risk by itself.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
esoul-cz/cqrs Version ^1.0 | — | — |
illuminate/support Version ^10.2|^11.0|^12.0|^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16.1 | — | — |
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.