Documentation, tests, licensing, and a matching source repository are in place. The project is not deprecated or archived, but its maintenance has effectively stopped, so future API and compatibility issues may go unaddressed.
42%
Total Score
25
75
75
The latest release was over six years ago, with no releases in the last 12 months. This is strong evidence of abandonment for an SDK that integrates with an external API.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no recent maintenance capacity.
Only one registry publishing account is listed, leaving a thin publishing base. This is a smaller concern than the observed inactivity, but it increases continuity risk for a user-owned project.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than evidence that the release is unsafe.
The repository is not archived, which preserves a path for maintenance, but its last push was over six years ago and does not offset the observed inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.0 | — | — |
illuminate/support Version ~5 | — | — |
bensampo/laravel-enum Version ^1.19 | — | — |
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.