Health-Check & Audit Tool for Composer Dependencies - Find out which packages are well-maintained, secure, and which ones to avoid.
61%
Total Score
caution
Usable with caveats: one release and no commits in the last three months suggest uncertain maintenance.
There were zero commits and zero active maintainers in the last three months, which is the strongest evidence that maintenance may have stalled after the initial release.
A post-autoload-dump lifecycle script runs during Composer installation, adding some install-time execution surface, though this is common for framework packages.
Only one registry publishing account is listed, leaving limited publishing redundancy; the repository is user-owned rather than organization-backed, so no broader operational backing is shown.
The package and repository are owned by the same individual account, confirming source ownership but not providing evidence of organizational maintenance capacity.
This is a 247-day-old package with only one release, so there is little evidence of an established release process or ongoing maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/prompts Version ^0.3.10 | — | — |
illuminate/contracts Version ^10.0|^11.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.