The single maintainer and no commits in the last three months reduce maintenance confidence. A clear README, repository tests, release notes, active organization backing, and a security policy provide useful support, while workflow pinning and permissions need attention.
61%
Total Score
63
100
88
83
Only one registry account has publish access, which limits publishing redundancy, although the organization-backed repository provides some compensation.
The package has existed for about 3 years and 11 months with seven releases, but only one release in the last 12 months and a median interval of about 192 days indicate a slow cadence.
The repository recorded zero commits and zero active maintainers in the last three months, a concrete sign that maintenance activity has slowed.
There are no open issues and two open pull requests, but no issues or pull requests were merged in the last month, providing little evidence of current response activity.
The current v0.2.4 release is not a prerelease, but the package remains below major version 1, which leaves more room for compatibility changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
laravel/framework Version ^12.0 || ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.93 | — | — |
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.