The repository has had no commits for nearly nine years, and only four releases were published. A clear MIT license, README, matching repository, and exact-version GitHub release improve transparency, but they do not offset the maintenance risk.
38%
Total Score
0
79
83
The package has made only four releases, all concentrated on its first day, with no release in nearly nine years. This is strong evidence of abandonment for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, with its last push nearly nine years ago. No provided evidence shows ongoing maintenance capacity.
Composer is used as the build tool, but no security scanning tools are configured. This is a minor hygiene gap and does not outweigh the direct evidence about release and commit inactivity.
The repository has no security policy. For a small, long-stale package this reduces transparency around vulnerability reporting, adding a modest concern beyond the much larger maintenance risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.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.