It has a clear MIT license, a README, and tests, but lacks a security policy and security scanning. Its small, single-author footprint leaves little evidence of current support.
40%
Total Score
50
75
75
The package has made four releases, all ending about 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being deprecated.
Only one registry publishing account is listed. A single maintainer is not inherently unhealthy, but it provides little redundancy for a project with no recent activity.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance history.
Composer is used for builds, but no security scanning tool is configured. For a small package this is a minor transparency gap, not evidence of a specific defect.
The linked repository is not marked archived, but its last push was about 12 years ago. The stale repository activity reinforces the release-history concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version 4.2.* | — | — |
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.