Tests, documentation, and a matching source repository make the package easier to assess. MIT licensing and a small dependency surface help, but the lone maintainer, absent security scanning, and unpinned workflow actions limit confidence.
54%
Total Score
33
100
67
75
There has been only one release, on April 12, 2023, and none in the last 12 months. This long period without another release is meaningful abandonment risk for a package still at its first version.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push, this is a substantial maintenance and abandonment concern.
One registry account has publish access. Because the repository is owned by an individual rather than an organization, this leaves a narrow publishing capacity and increases bus-factor concern.
The package and repository are backed by the same individual account, so the source relationship is coherent. There is no organizational backing shown to compensate for the narrow maintainer base.
The repository has 2 stars, 0 forks, and 1 watcher. Low adoption is only supporting evidence, but it provides little external validation or community resilience.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.0 || ^10.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.