Clear documentation, repository tests, licensing, and a matching source tree improve confidence. The workflow leaves all four actions unpinned, while security coverage is limited and recent development comes from one contributor.
68%
Total Score
50
100
88
75
The repository is owned by an individual rather than an organization, so the single-contributor activity and bus factor represent actual continuity risk rather than normal organizational publishing structure.
The package has five releases across roughly four years, with one release in the last 12 months and a median interval of about 13 months. The recent release shows the project is not abandoned, but the slow cadence limits maintenance confidence.
All recent commits came from one contributor, giving the project a high maintenance concentration. A single maintainer can still sustain a small package, but handoff and continuity risk are real.
There was one commit in the last three months, so the project is still receiving activity, but the volume is too low to demonstrate strong ongoing maintenance.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.93.1 | — | — |
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.