gehrisandro/tailwind-merge-laravel
Maintenance rests on one registry publisher and no commits in the last three months. The repository is current, tests and release notes are present, but absent security scanning and six unpinned workflow actions add upkeep risk.
67%
Total Score
75
100
89
75
Health Score Breakdown
Only one account has registry publishing access, leaving release continuity dependent on a single publisher; the linked repository is also user-owned rather than organization-backed.
The package has existed for about 3 years and released once in the last 12 months; the latest release is recent, but the current cadence is modest.
The repository recorded zero commits and zero active maintainers in the last three months, a meaningful maintenance warning even though the release itself was recent.
Composer build tooling is present, but no security scanning tools were detected, leaving automated security coverage weaker than it could be.
The repository has no published security policy, making vulnerability reporting and response expectations less transparent.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Sandro Gehri |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.5.1 | — | — |
laravel/framework Version ^12.0|^13.0 | — | — |
gehrisandro/tailwind-merge-php Version ^v1.1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 months ago
- Created
- 3 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.