Two registry maintainers and organization backing provide some ownership context, while the modest dependency set and absent install scripts reduce operational friction. Documentation and security-process coverage are thin.
38%
Total Score
50
100
50
75
The manifest declares the package proprietary, but no license file was found in either the artifact or repository. That creates a material adoption and redistribution concern for a package presented as open source.
Only two releases were published, both on May 4, 2022, with no release in roughly four years and none in the last 12 months. This is strong evidence of abandonment risk for a Laravel library.
The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap. No provided activity signal compensates for this lack of recent maintenance.
The published artifact has no README, and the linked project has no tests or changelog. Missing tests and changelog are normal for published artifacts, but the absent README is a minor integration and transparency gap for a library.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a secondary transparency weakness rather than evidence of a security issue by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version >=5.7 | — | — |
guzzlehttp/guzzle Version >=6.5 | — | — |
illuminate/support Version >=5.7 | — | — |
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.