Clear documentation, release notes, and recent commits support ongoing maintenance. A security policy and clean workflow audit help, though the project remains dependent on one active contributor.
72%
Total Score
63
100
94
88
Only one registry account has publish access. That is a modest operational resilience concern, though repository activity confirms the account is actively maintaining the project.
The repository is owned by an individual account rather than an organization, so the single-contributor concentration is not offset by visible organizational backing.
All six recent commits came from one contributor, leaving no demonstrated handoff capacity if that maintainer becomes unavailable.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than evidence of unsafe code.
Both workflows were analyzed without failed files, dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all six action references are unpinned and one workflow grants top-level write permission, creating a workflow-reproducibility and least-privilege caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/forms Version ^4.0|^5.0 | — | — |
spatie/laravel-package-tools Version ^1.15.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.