It has a clear README, repository tests, and a real release record. A one-person project without a security policy leaves less support if maintenance stops.
62%
Total Score
67
100
94
50
Only one account has registry publish access. The matching user-owned repository provides some continuity, but the narrow publishing base increases dependence on one maintainer.
The package is young at 164 days, with seven releases concentrated over roughly 10 days. That shows initial activity but provides limited evidence of long-term maintenance.
The repository recorded zero commits and zero active maintainers during the last three months. That is a meaningful maintenance warning for a package only about five months old.
The repository has no security policy. This is a transparency and incident-response gap, though it is not by itself evidence that the package is unsafe.
All five analyzed workflow action references are unpinned, reducing build reproducibility. One workflow grants top-level write access, but there are no untrusted checkouts, script injections, or high-confidence audit findings, so this remains a hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^4.3.1|^5.0 | — | — |
spatie/laravel-package-tools Version ^1.15 | — | — |
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.