The repository has a clear README, thorough tests, release notes, and a matching source project. There is no security policy, and the two workflow actions are unpinned, so maintenance and build hygiene deserve attention.
72%
Total Score
50
100
94
75
The package and repository are owned by the same individual account rather than an organization. That is coherent ownership, but it indicates a limited formal backing structure.
There were no commits and no active maintainers in the last three months, despite the recent release. This suggests maintenance has paused after the release and is the main adoption concern.
Only two issues and one pull request are open, with little activity in the last month. The low issue volume is not concerning by itself, but it provides limited evidence of active community support.
Composer build tooling is present, but no security scanning tools were detected. For a small PHP library this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy. This weakens vulnerability-reporting transparency, although the package's license, tests, and recent release provide some compensating project evidence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^12.0|^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.