46%
Total Score
unhealthy
Risky: no releases or commits for over a year, with only two releases and no active maintainers visible.
Only two releases were published, both about 570 days ago, with no releases in the last 12 months. This strongly suggests the package may be abandoned, despite the absence of registry deprecation.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. This is substantial evidence of stalled maintenance.
The repository is owned by an individual user rather than an organization. That is normal for a small package, but it offers less visible institutional backing to compensate for the inactive maintenance record.
The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small package, but these values provide little supporting evidence of adoption or community resilience.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and transparency gap, though not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sajya/server Version * | — | — |
illuminate/console Version * | — | — |
illuminate/support Version * | — | — |
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.