Documentation and release notes make integration straightforward, while the repository has tests, a changelog, security policy, and pinned workflow actions. The project is too new to demonstrate a sustained maintenance record, and publishing rests with one maintainer.
72%
Total Score
50
100
93
100
Only one registry account publishes the package, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is limited visible redundancy if that maintainer becomes inactive.
The package and repository share the same individual owner, which supports attribution but does not provide the redundancy of organization backing.
The package is brand new, with three releases published on the same day and no established release interval. This limits evidence of sustained maintenance, though it does not indicate abandonment by itself.
No commits or active maintainers were recorded during the past three months. Because the package was released today, this is limited evidence rather than proof of abandonment, but it leaves ongoing maintenance unestablished.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^5.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
jeffersongoncalves/laravel-sso-client Version ^1.1 | — | — |
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.