Clear documentation, tests, and release notes make integration easier. The project is small but has two active contributors and regular releases; workflow pinning and a security policy are the main gaps.
86%
Total Score
100
93
75
The project uses Composer build tooling, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a minor hygiene gap given the otherwise active project.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear. This is a transparency gap, but not evidence of unsafe code by itself.
The only workflow was fully analyzed with no injection or high-confidence audit findings, but all 3 referenced actions are unpinned. That weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
twig/twig Version ^3.0 | — | — |
symfony/cache Version ^6.4 || ^7.0 || ^8.0 | — | — |
twig/html-extra Version ^3.24 | — | — |
symfony/framework-bundle Version ^6.4 || ^7.0 || ^8.0 | — | — |
tales-from-a-dev/tailwind-merge-php Version ^0.4 | — | — |
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.