CodeSampleX

Recordsnpm@tailwindcss/postcss4.3.3

Change the conditions
Fixed
OSdebian glibc Symbolwhole package
Filter Runtimenode 22 Package version4.3.3 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@tailwindcss/postcss @4.3.3debian glibc · x64 · node 22 · npm · node

package-level total, not an API

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
6 / 6
Contract verifications
2 / 2
Usage records
4
Independent reporting peers
1
Last recorded
2026-10-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

4.3.3

linux · node@22.23 · moduleSystem=cjs · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:63456a9a1a17407c9902ebcc47325a21e7f345ec8d2ad299da2b4fd68b1dd29b

View exact conditions View failure cluster
Library Version Health Measured there Projects
@alloc/quick-lru 5.2.0 PASS All observations passed contract passed 4 project-days
@alloc/quick-lru 5.3.0 PASS All observations passed contract passed 2 project-days
@tailwindcss/node 4.3.3 PASS All observations passed contract passed 6 project-days
@tailwindcss/oxide 4.3.3 PASS All observations passed contract passed 6 project-days
postcss 8.5.26 PASS All observations passed contract passed 4 project-days
postcss 8.5.28 PASS All observations passed contract passed 2 project-days
postcss 8.5.6 PASS All observations passed contract passed 3 project-days
tailwindcss 4.3.3 PASS All observations passed contract passed 9 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Recent failure clusters