Rules enforcing best practices while using Tailwind CSS
72%
Total Score
75
100
94
75
50
No build attestation or trusted-publisher provenance is recorded, so consumers have less evidence connecting the published artifact to its source build.
The repository is owned by an individual rather than an organization, so the concentrated recent contribution pattern is not offset by visible organizational backing.
Four contributors were active in the last three months, but the leading contributor made 46 of 49 commits, or about 94%, creating a meaningful continuity risk despite recent activity.
The project uses TypeScript, Vitest, unbuild, and npm scripts, but no security-scanning tool was detected. The build and test tooling is a positive, while the missing scanning coverage is a modest hygiene gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
postcss Version ^8.4.4 | — | — |
synckit Version ^0.11.11 | — | — |
postcss-nested Version ^7.0.2 | — | — |
tailwind-api-utils Version ^1.0.3 | — | — |
@typescript-eslint/utils Version ^8.37.0 | — | — |
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.