The small audience and single-person ownership limit visible resilience, while the repository remains active enough to publish a current stable release. A clear license, repository tests, release notes, and matching source reduce adoption risk.
62%
Total Score
50
83
67
Only one registry account has publish access, and the repository is user-owned rather than organization-backed. This is a modest resilience concern, especially alongside the lack of recent commit activity.
The registry namespace and repository are owned by the same individual, confirming direct ownership but not providing organizational backing to compensate for a thin maintainer base.
The package has existed for nearly four years and has 15 releases, but only one release appeared in the last 12 months. That points to slower maintenance despite the recent release.
There were no commits and no active maintainers in the last three months. A recent release partly offsets this, but the current development gap remains a maintenance concern.
The repository has only 2 stars, no forks, and 1 watcher. This is limited supporting evidence for community depth, but it is not by itself an abandonment verdict.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/database Version ^11.0|^12.0|^13.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.