A single maintainer, no security policy, and four unpinned workflow actions reduce confidence in long-term upkeep. The package is documented, tested, licensed, and not archived, which supports continued use despite the maintenance slowdown.
60%
Total Score
50
75
50
The package runs a post-autoload-dump install-time script, adding execution during installation. This is a supply-chain hygiene consideration, though the signal alone does not show unsafe behavior.
One registry maintainer is consistent with a user-owned project, but it leaves little visible publishing redundancy if that person becomes unavailable.
Only two releases exist, with no release in about 18 months and none in the last 12 months. This suggests maintenance has slowed, although a small package may not need frequent releases.
There were no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This is the strongest evidence that active maintenance has slowed.
The repository uses Composer build tooling but reports no security scanning tools. That limits automated security hygiene, though it does not establish a defect in the package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
filament/filament Version ^3.1.0 | — | — |
illuminate/contracts Version ^10.0|^11.0|^12.0 | — | — |
spatie/laravel-package-tools Version ^1.13.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.