The repository has had no commits in the last 3 months, and its security policy is missing. MIT licensing, tests, a changelog, and a matching repository provide useful transparency, but the package remains early-stage at 0.2.0.
58%
Total Score
50
100
81
50
One registry maintainer is consistent with a user-owned repository, but it leaves the project dependent on a single publisher.
The registry namespace and repository are owned by the same individual, providing clear ownership but no organizational backing or broader maintenance base.
The package has only two releases, with the latest about 17 months ago and no releases in the last 12 months. This indicates weak recent maintenance momentum.
There were no commits and no active maintainers in the last 3 months. Combined with the old latest release, this raises abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence of a serious defect by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.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.