The project has a clear license, regular release history, stable versioning, and matching repository documentation. A single maintainer, no recent commits, and no security policy leave less evidence of ongoing support.
68%
Total Score
63
100
94
83
Only one registry publishing maintainer is listed. This limits publishing redundancy, although the repository is independently linked to the same named owner.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, so there is no organizational backing to offset the thin maintainer base.
The repository recorded zero commits and zero active maintainers in the last three months. Despite recent release history, this weakens evidence that maintenance is continuing now.
Composer is used for builds, but no security scanning tool was detected. The missing scanner is a modest transparency and hygiene gap rather than evidence of abandonment.
The repository has no security policy. That makes vulnerability reporting less transparent, though it is not by itself a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version ^4.7 | — | — |
beebmx/blade Version ^1.8 | — | — |
illuminate/view Version ^10.0|^11.0|^12.0 | — | — |
getkirby/composer-installer Version ^1.2 | — | — |
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.