A clear README, permissive license, and small dependency footprint make integration straightforward. The project has had no release or commit activity for over four years, and its single-person backing leaves future fixes uncertain. There is also no security policy.
58%
Total Score
50
100
92
50
Only one registry maintainer is listed, and the project backing identifies a user-owned repository rather than an organization. That suggests limited redundancy if the maintainer becomes unavailable.
The latest release was over four years ago, with no releases in the last 12 months. Earlier releases were reasonably spaced, but the long current gap raises abandonment and compatibility concerns.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release pause. This materially lowers confidence in ongoing maintenance.
The repository has no published security policy. For a small package this is not severe by itself, but it reduces transparency about reporting and handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~7|~8|~9 | — | — |
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.