The repository lacks a security policy and security-scanning tools, while all eight workflow actions are unpinned. A clear README, changelog, comprehensive tests, matching repository, and MIT licensing provide useful transparency and adoption support.
68%
Total Score
50
100
83
75
The repository recorded zero commits and zero active maintainers during the last three months, which raises a maintenance and abandonment concern despite a recent release.
There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a small project, but provides little evidence of active community maintenance.
The repository has zero stars and forks and one watcher, providing little community validation. Popularity is supporting evidence only, so this modestly lowers confidence rather than determining the health verdict.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is partly offset by the package's visible source repository and testing setup, but it still reduces transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^10.0|^11.0|^12.0 | — | — |
spatie/laravel-package-tools Version ^1.13.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.