The project has clear documentation, tests in the repository, a matching source repository, and an MIT license. Its single-release history, no recent commits, missing security policy, and unpinned workflow actions leave maintenance and build-integrity concerns.
61%
Total Score
50
79
50
This is the only release, published about 11 months ago, so there is little evidence of an established maintenance pattern.
There were no commits and no active maintainers in the last 3 months, leaving maintenance continuity uncertain despite the repository being active after the initial release.
The repository uses Composer build tooling, but no security scanning tools were detected, leaving a modest transparency and review gap.
The repository has no security policy, so it provides no documented channel or process for reporting vulnerabilities.
The current version is v0.1.0 and is not a stable major release, which is consistent with an early-stage package and raises compatibility risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/scout Version ^10.11 | — | — |
illuminate/contracts Version ^10.0||^11.0||^12.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.