The project is small, with no security policy or automated security scanning, so long-term support depends heavily on its sole maintainer. Its MIT license, focused dependency set, matching repository, and usable README provide useful transparency.
62%
Total Score
50
100
83
75
The registry and repository are owned by the same individual account rather than an organization, so the small maintainer base represents the project's actual backing.
The package has only 3 releases and none in the last 12 months; its latest release was about 18 months ago. This indicates limited and currently inactive release maintenance.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. Combined with no releases in the last 12 months, this is meaningful evidence of inactive maintenance.
The repository has 0 stars, 0 forks, and 1 watcher, indicating little independent adoption or community reinforcement. Popularity is supporting evidence, so this lowers confidence in project resilience rather than making the package unfit alone.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap for a small package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.0|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0|^12.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.