76%
Total Score
75
100
88
88
The package uses a post-autoload-dump Composer lifecycle script. This is a mild supply-chain consideration, but the signal does not show that the script is unsafe or unusually extensive.
Only one account has registry publishing access. That is a limited publishing base, although registry access alone does not establish the repository's maintenance capacity.
One contributor made all three commits in the last three months, creating a concentrated active contributor base. Organization ownership partly compensates because maintenance can potentially be handed off internally.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a hygiene gap rather than evidence of abandonment.
Version v0.13.1 is not marked as a prerelease, but the package remains below 1.0. Consumers should allow for compatibility changes between releases.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
sqids/sqids Version ^0.5.0 | — | — |
illuminate/database Version ^11.0|^12.0|^13.0 | — | — |
illuminate/contracts Version ^11.0|^12.0|^13.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.