The repository is intact, tested, and clearly matches the package, with a simple dependency surface. One maintainer, no recent commits, and no security policy leave future compatibility support uncertain.
60%
Total Score
50
100
88
50
A single registry maintainer is consistent with this user-owned project, but it leaves limited visible publishing capacity and creates a higher bus-factor concern.
The registry namespace and repository are owned by the same individual, and the repository is user-owned rather than organization-backed. This supports clear ownership but does not compensate for the thin maintainer base.
The package has had no release in more than four years, with zero releases in the last 12 months. Its earlier history shows established development, but the long gap raises abandonment and compatibility concerns.
There were no commits and no active maintainers in the last three months. Together with the absence of releases since April 2022, this indicates very limited current maintenance.
The project uses Composer for its build, but no security-scanning tools were detected. The missing scanning is a modest transparency and maintenance gap rather than evidence of an unsafe release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^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.