The single registry maintainer and lack of automated security scanning leave less resilience if ownership or defects become a problem. Recent releases, an unarchived organization-backed repository, and project tests provide useful counterweight.
67%
Total Score
67
100
93
50
The package runs a post-autoload-dump install-time script, adding execution during Composer installation and therefore a modest supply-chain exposure.
Only one account has registry publish access, which is a resilience concern, although the repository is owned by an organization that provides some backing.
The repository recorded zero commits and zero active maintainers in the last three months, indicating a recent pause in development despite the broader release history.
Composer build tooling is present, but no security-scanning tools were detected, leaving automated security coverage incomplete.
No repository security policy was found, reducing transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/laravel-package-tools Version ^1.14.0 | — | — |
gehrisandro/tailwind-merge-laravel Version ^1.3 | — | — |
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.