The small, focused codebase has clear documentation, a matching repository, and an MIT license. Its long period without releases or commits, together with no tests or security policy, makes long-term compatibility support uncertain.
42%
Total Score
0
100
75
75
The latest release was over 8 years ago, with no releases in the last 12 months; this is strong evidence of stalled maintenance. The package’s four-release history shows it was once published, but does not offset the prolonged inactivity.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the release history’s long inactivity. The repository is not archived, but there is no observed recent development to compensate.
Composer is used as the build tool, but no security scanning tools are configured. The conventional build setup is positive; the missing scanning is a minor transparency and maintenance gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a maintenance and transparency gap, though it is less severe than the lack of recent development.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
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.