A single-person project with no security policy and seven unpinned workflow actions leaves less maintenance and build assurance. Clear licensing, tests, release notes, and a focused dependency set provide useful transparency.
61%
Total Score
50
100
86
75
Only one registry maintainer is listed, and the project is backed by an individual rather than an organization. That leaves limited visible publishing redundancy.
The registry namespace and repository are owned by the same individual, which supports coherent ownership but provides no organizational backing or visible redundancy.
The package has six releases since September 2024, but none in the last 12 months; the latest release was over a year ago. This indicates a meaningful maintenance slowdown.
There were zero commits and zero active maintainers in the last three months, consistent with the broader release pause and increasing abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest assurance gap, not evidence of a defect.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0 | — | — |
illuminate/support Version ^10 || ^11 || ^12 | — | — |
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.