A single maintainer and no security scanning reduce resilience for a small integration package. The MIT license, README, and matching repository provide useful transparency, but they do not offset the prolonged inactivity.
42%
Total Score
25
81
The package has 41 releases, but its latest release was about two years ago and it had no releases in the last 12 months, indicating prolonged abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing that development is currently inactive.
One registry maintainer creates a thin publishing base and increases continuity risk, although the linked repository is owned by the same individual.
Composer build tooling is present, but no security scanning tools were detected, leaving a meaningful maintenance and review gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.2 | — | — |
laravel/framework Version ^10.10 | — | — |
yaangvu/laravel-base Version ^4.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.