Clear documentation, tests, release notes, and security reporting support adoption. Maintenance has recently gone quiet, while workflow checks need tightening before relying on automated publishing or merges.
68%
Total Score
50
100
100
100
Only one registry account has publish access, which creates a thin publishing base, although the repository and release history show an identifiable active owner.
The package and repository are owned by the same individual account rather than an organization, so the single-owner maintenance risk is material.
The repository recorded zero commits and zero active maintainers in the last three months, a concrete sign that maintenance has recently slowed despite the recent push and release history.
There are no open issues or pull requests and no issue or pull-request activity in the last month; this is not inherently negative, but it provides little evidence of current community support.
All three workflows were analyzed, but all seven action references are unpinned and the Dependabot auto-merge workflow has a high-confidence bot-conditions finding plus top-level write permissions. There is no untrusted checkout or script injection, which limits the severity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/widgets Version ^4.0|^5.0 | — | — |
filament/filament Version ^4.0|^5.0 | — | — |
illuminate/support Version ^11.28|^12.0|^13.0 | — | — |
spatie/laravel-analytics Version ^5.5 | — | — |
spatie/laravel-package-tools Version ^1.9 | — | — |
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.