All eslint-plugin-tailwind-canonical-classes versions
eslint-plugin-tailwind-canonical-classes @1.0.8
rejected
This version was rejected.
It did not pass GreenFlagged's security review and is not served by the registry.
The findings and risk dispositions below explain why.
25
Risk Score
MIT
License
No
Install Scripts
1
Dependencies
1
Dev Dependencies
5.2 KB
Package Size
Published
ESLint plugin to enforce canonical Tailwind CSS class names using Tailwind CSS v4's canonicalization API
Maintainers
maisonnat_maxence
Keywords
eslinteslint-plugintailwindtailwindcsscanonicallintcss
Dependencies (1)
| Package | Constraint | Registry Status |
|---|---|---|
| @tailwindcss/node | ^4.0.0 | auto_approved |
Dev Dependencies (1)
| Package | Constraint | Registry Status |
|---|---|---|
| eslint | ^9.0.0 | auto_approved |
Transitive Dependency Tree
14 transitive deps
max depth 5
├─
@tailwindcss/node
^4.0.0
→ 4.2.4
├─
@jridgewell/remapping
^2.3.5
→ 2.3.5
├─
enhanced-resolve
^5.19.0
→ 5.22.1
├─
jiti
^2.6.1
→ 2.6.1
├─
lightningcss
1.32.0
├─
magic-string
^0.30.21
→ 0.30.21
├─
source-map-js
^1.2.1
→ 1.2.1
├─
tailwindcss
4.2.4
→ 4.2.4
├─
@jridgewell/gen-mapping
^0.3.5
→ 0.3.13
├─
@jridgewell/sourcemap-codec
^1.5.5
→ 1.5.5
├─
@jridgewell/trace-mapping
^0.3.24
→ 0.3.31
├─
graceful-fs
^4.2.4
→ 4.2.11
├─
tapable
^2.3.3
→ 2.3.3
├─
@jridgewell/resolve-uri
^3.1.0
→ 3.1.2
├─
@jridgewell/sourcemap-codec
^1.5.0
→ 1.5.5
├─
@jridgewell/sourcemap-codec
^1.4.14
→ 1.5.5
├─
@jridgewell/trace-mapping
^0.3.24
→ 0.3.31
├─
@jridgewell/resolve-uri
^3.1.0
→ 3.1.2
├─
@jridgewell/sourcemap-codec
^1.4.14
→ 1.5.5
Changes from v1.0.7
No metadata changes detected.
File Changes
0 added
0 removed
2 modified
size delta: +1.1 KB
Risk Dispositions (1 applicable to this version, 0 other)
Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.
| Rule | Source | Disposition | Author | Reason | |
|---|---|---|---|---|---|
regressed-provenance |
provenance | reject | AI | AI (provenance): Provenance regression on a package that consistently published with CI attestations is a strong compromise signal. |
SAST Findings (1)
HIGH
Provenance attestation missing — previous versions had it
provenance
This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
Review Summary
Risk score: 25. Findings: 1 high (+25).
Commit: 02a76e2bd7c4 Browse source
Published to npm: