Healthy and suitable to depend on, with a narrow maintenance risk. It has frequent releases, a current non-archived repository, tests and release notes, but recent activity is concentrated in one contributor and the repository lacks a security policy.
82%
Total Score
70
100
94
67
Only one registry account has publish access, which is a supply-chain continuity concern, although the repository is organization-owned and shows active project backing.
All one recent commit came from a single contributor, giving a 100% top-contributor share. Organization backing reduces the impact because work can potentially be handed off, but no second active contributor is shown.
The repository recorded one commit in the last three months, while the registry shows 27 releases in the last year. Releases demonstrate activity, but the low recent commit count makes ongoing source maintenance less certain.
The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a transparency gap, though it is not by itself evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a maintained library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/contracts Version ^11.0|^12.0|^13.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.