The MIT license, consumer README, repository tests, and matching source make adoption clearer. Composer tooling is present, but there is no security policy or automated security scanning, so ongoing oversight is limited.
57%
Total Score
25
100
78
83
The package has only three releases, all concentrated between April 16 and April 19, 2023, with no releases in roughly three years. This is strong evidence of stalled maintenance for a library dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having received no updates since April 2023. This materially increases abandonment risk.
The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the single-maintainer and inactivity concerns.
The repository has two stars, no forks, and no watchers. Low popularity is supporting evidence rather than a verdict, but it means there is little visible community adoption to compensate for stalled maintenance.
Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a modest transparency and maintenance gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^7.0||^8.0||^9.0||^10.0 | — | — |
illuminate/filesystem Version ^7.0||^8.0||^9.0||^10.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.