Server-rendered Blade, Livewire and daisyUI screens for laravel-mutable-content: forms, tables and management of fields and lists of values.
72%
Total Score
caution
A brand-new package has four rapid releases, while every workflow action remains unpinned.
One registry account has publish access, but the repository is owned by the same individual and is actively publishing releases. The narrow base limits redundancy without indicating abandonment.
The registry namespace and repository owner match a personal account. This is consistent ownership, though it does not provide organizational backing for a package that is still very new.
The package was first released today and has four releases in roughly 8 hours, with a median interval of about 1 hour 42 minutes. This shows active initial work but provides too little history to establish durable maintenance.
Version v0.3.1 is not a stable major release, so compatibility may still change. It is not marked as a prerelease, which partly offsets the concern.
The only workflow was fully analyzed with no injection sinks or audit findings, but all 4 action references are unpinned. That leaves builds exposed to unreviewed action changes and is a real reproducibility concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
livewire/livewire Version ^4.0 | — | — |
mallardduck/blade-lucide-icons Version ^2.0 | — | — |
amarenkov/laravel-mutable-content Version ^0.7.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.