The repository has no security scanning or published security policy, reducing transparency. The package is licensed, documented, non-deprecated, and its repository remains active, but the registry has had no release in over five years and recent commit activity is absent.
58%
Total Score
50
100
88
75
The repository is owned by a user account rather than an organization, so the small registry maintainer list has no visible organizational backing to offset the maintenance concerns.
The package has had no release in over five years, with zero releases in the last 12 months; this is a meaningful maintenance concern despite the repository being updated later.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the concern raised by the long registry release gap.
Composer build tooling is present, but no security scanning tools were detected, leaving automated security checks unconfirmed.
The repository has no security policy, so its process for receiving and handling vulnerability reports is not documented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.0|~6.0|~7.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.