Testing, a README, release notes, and organization backing provide useful signs of a real project. However, the package has no recent commit activity, and both workflow actions are unpinned.
42%
Total Score
50
100
75
50
The latest release was in December 2023, with no releases in the last 12 months despite the package being nearly three years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance between releases.
Only one registry account can publish releases, which is a modest resilience concern. The organization-owned repository provides some backing, so this is not a severe maintainer-risk signal.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a hygiene concern, not evidence that the package is unsafe.
Version v0.1.4 is not a stable-major release, which signals a relatively immature API. The absence of prerelease labeling partly offsets this, but not the low version line.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8 | — | — |
laravel/framework Version ^10.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.