The README, MIT licensing, and simple dependency set support straightforward adoption. A single individual backs the project, and the repository has no security policy or scanning tools, limiting maintenance transparency.
58%
Total Score
50
100
83
75
Only one registry maintainer is listed, and the project is backed by an individual account rather than an organization. This creates a thin continuity base if the maintainer becomes unavailable.
The package has made only one release, first published about 2 years and 10 months ago, with no releases in the last 12 months. That leaves its maintenance trajectory uncertain.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with a project that is currently inactive.
Composer build tooling is present, but no security scanning tools are configured. The simple package scope limits the impact, but automated security coverage is absent.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap for a dependency used in applications.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.0|^9.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.