The README, tests, and Composer build setup provide basic project transparency. No security scanning and a single maintainer leave little evidence of support beyond the original author.
32%
Total Score
33
81
75
The package has only two releases, both in January 2014, and none in the last 12 months; the latest release is over 12 years old. This is strong evidence of abandonment.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and showing no recent maintenance.
Only one registry maintainer is listed. The linked repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops supporting the package.
There were no new or closed issues or pull requests in the last month. With no recent release or commit activity, this provides no evidence of an active support channel.
Composer is used as the build tool, which is appropriate for a Packagist package, but no security scanning tools are present. That is a minor transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version 4.1.* | — | — |
illuminate/database Version 4.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.