The package has a clear artifact, repository tests, a changelog, and steady releases over the past year. Maintenance and security oversight remain thin because all recent commits come from one contributor, with no security policy or scanning tools.
68%
Total Score
67
100
94
67
A post-autoload-dump install-time script adds some execution and review surface, though this is a common Composer package mechanism and no other evidence indicates misuse.
The repository is owned by an individual user rather than an organization, so the single-contributor concentration has no visible organizational backing to compensate for it.
All six recent commits came from one contributor, so maintenance depends heavily on a single person and has limited handoff resilience.
Composer build tooling is present, but no security-scanning tools were detected, leaving security oversight less transparent.
The repository has no security policy, making vulnerability reporting and response expectations less clear for consumers.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^12.0||^13.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.