The small codebase and absent security policy leave limited evidence of mature maintenance practices. MIT licensing and a usable README help adoption, but they do not offset the long maintenance gap.
44%
Total Score
0
100
79
67
Only two releases exist, both published in April 2022, with no release in more than four years. This is strong evidence of abandonment risk for a package intended for ongoing application use.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the multi-year release gap. There is no provided activity signal showing renewed maintenance.
The published artifact and repository each contain only nine files, indicating a very small implementation with limited surrounding project material. That is not inherently unsafe, but it provides little evidence of maturity for a framework integration.
The linked repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it is less severe than the sustained lack of maintenance.
The latest release is v0.2, so the package has not reached a stable major version. Combined with the lack of subsequent releases, this increases compatibility and maintenance uncertainty.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.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.