The package is clearly licensed, documented, and backed by a matching repository. It has repository tests and no install scripts, but lacks a security policy.
43%
Total Score
50
81
75
The latest registry release was published about 9 years ago, and there were no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having 22 historical releases.
There were no commits and no active maintainers in the last 3 months. Combined with the old registry release, this materially increases maintenance and abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented for a package intended to address dependency security.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~6.0 | — | — |
illuminate/console Version ~5.0 | — | — |
illuminate/support Version ~5.0 | — | — |
tightenco/mailthief Version 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.