The README and MIT license make its purpose and usage clear. Missing security policy and scanning leave little evidence of ongoing project care.
35%
Total Score
0
75
75
The package has made no release in nearly 10 years: its latest release was in June 2016, with zero releases in the last 12 months. This is strong evidence of abandonment despite the stable 1.2.0 version.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history showing that maintenance stopped years ago.
Composer build tooling is present, but no security-scanning tools are configured. That is a modest maintenance and assurance gap, not evidence of malicious behavior by itself.
The repository has no security policy, reducing transparency for reporting and handling issues. This matters more for an inactive package because there is little evidence that security concerns would be addressed.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.0 | — | — |
illuminate/console Version ~5.1 | — | — |
illuminate/support Version ~5.1 | — | — |
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.