The package is well documented, tested, licensed, and has a matching source repository. Its maintenance record is still very short, with no commits in the past three months and all workflow actions unpinned.
62%
Total Score
67
100
88
83
Registry publishing access is held by one individual. The matching user-owned repository provides some continuity, but the single-person publishing base leaves limited evidence of maintenance redundancy.
Only two releases exist, both published about 30 minutes apart, and the package is roughly 103 days old. This is limited evidence of an established release process, though the package is still new.
The repository recorded zero commits and zero active maintainers during the past three months. Because the package is only about 103 days old, this indicates a thin and currently inactive maintenance record rather than definitive abandonment.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, although it does not by itself show that the package is unmaintained.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
league/commonmark Version ^2.0 | — | — |
livewire/livewire Version ^3.6|^4.0 | — | — |
illuminate/support Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.0 | — | — |
codeat3/blade-phosphor-icons Version ^2.4 | — | — |
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.