The README is substantial, and the package has a matching repository, MIT licensing, and no install-time scripts. Its lone maintainer, absent security scanning, and lack of a security policy leave less assurance than a mature project.
70%
Total Score
50
100
88
75
One individual account has registry publish access, which leaves a thin publishing base and creates some continuity risk. The matching user-owned repository shows direct project ownership but does not remove the single-maintainer limitation.
All three releases were published within roughly 3 hours, and no later release activity is shown across the package's 208-day history. That short, burst-like history provides limited evidence of sustained maintenance.
Composer is used as the build tool, but no security-scanning tooling is reported. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a package that integrates with application deletion controls, this reduces clarity about vulnerability reporting and maintenance response.
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 | — | — |
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.