Clear licensing, tests, and release notes provide a solid foundation. The very short release history, eight months without commits, and unpinned workflow actions leave maintenance and build-integrity concerns.
55%
Total Score
50
100
88
67
A post-autoload-dump Composer lifecycle script runs during installation-related operations. This is a supply-chain consideration, though the signal does not show that the script is malicious or unusually broad.
The package and repository are owned by the same individual account, so there is no organizational backing shown to compensate for the thin maintenance history.
The package has only two releases, both published on the same day, and no later release activity over roughly eight months. That gives little evidence of an established maintenance pattern.
There were no commits and no active maintainers in the last three months, consistent with the repository having stopped after its initial releases. This materially raises abandonment risk.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^3.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.