The small maintainer and contributor base limits visible maintenance capacity, while the repository has no security scanning or policy. Clear licensing, a usable README, and a non-archived source repository provide useful transparency.
58%
Total Score
50
100
83
83
Only one registry account has publish access. The repository is user-owned rather than organization-backed, so there is little visible publishing redundancy.
The package has only 4 releases since November 2018 and none in the last 12 months; its latest release was in September 2025. This indicates an unusually sparse and currently inactive release cadence.
The repository recorded zero commits and zero active maintainers in the last 3 months, providing direct evidence that maintenance has currently paused.
The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these counters provide no community-maintenance signal to offset the inactivity.
Composer is used for the build, but no security scanning tools are configured. The missing scanning is a hygiene weakness rather than evidence that the release is unsafe.
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.