CodeSampleX

Recordsnpmtailwindcss3.4.17

Change the conditions
Fixed
Package version3.4.17 Symbolwhole package
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

tailwindcss @3.4.17alpine musl · x64 · node 22 · npm · node

package-level total, not an API

8 of 8 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 (3)

Project observations
6 / 6
Contract verifications
8 / 8
Usage records
4
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Changed 5 · Steady 15

Dependency changes observed: 5. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
postcss 8.4.49 CHANGED Version changed, no linked failure contract passed 1 project-day
postcss-load-config 4.0.2 CHANGED Version changed, no linked failure builds observed 1 project-day
postcss-selector-parser 6.1.4 CHANGED Version changed, no linked failure builds observed 1 project-day
resolve 1.22.12 CHANGED Version changed, no linked failure contract passed 1 project-day
sucrase 3.35.1 CHANGED Version changed, no linked failure builds observed 1 project-day
@alloc/quick-lru 5.2.0 PASS All observations passed contract passed 1 project-day
arg 5.0.2 PASS All observations passed contract passed 1 project-day
chokidar 3.6.0 PASS All observations passed contract passed 1 project-day
didyoumean 1.2.2 PASS All observations passed contract passed 1 project-day
dlv 1.1.3 PASS All observations passed contract passed 1 project-day
fast-glob 3.3.3 PASS All observations passed contract passed 1 project-day
glob-parent 6.0.2 PASS All observations passed contract passed 1 project-day
is-glob 4.0.3 PASS All observations passed contract passed 1 project-day
lilconfig 3.1.3 PASS All observations passed contract passed 1 project-day
micromatch 4.0.8 PASS All observations passed contract passed 1 project-day
normalize-path 3.0.0 PASS All observations passed contract passed 1 project-day
picocolors 1.1.1 PASS All observations passed contract passed 1 project-day
postcss-import 15.1.0 PASS All observations passed contract passed 1 project-day
postcss-js 4.1.0 PASS All observations passed contract passed 1 project-day
postcss-nested 6.2.0 PASS All observations passed contract passed 1 project-day

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.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library3.4.183.4.17
postcss 8.5.6 8.4.49
postcss-load-config 6.0.1 4.0.2
postcss-selector-parser 6.1.2 6.1.4
resolve 1.22.11 1.22.12
sucrase 3.35.0 3.35.1
@alloc/quick-lru 5.2.0 5.2.0
arg 5.0.2 5.0.2
chokidar 3.6.0 3.6.0
didyoumean 1.2.2 1.2.2
dlv 1.1.3 1.1.3
fast-glob 3.3.3 3.3.3
glob-parent 6.0.2 6.0.2
is-glob 4.0.3 4.0.3
jiti 1.21.7 —
lilconfig 3.1.3 3.1.3
micromatch 4.0.8 4.0.8
normalize-path 3.0.0 3.0.0
object-hash 3.0.0 —
picocolors 1.1.1 1.1.1
postcss-import 15.1.0 15.1.0
postcss-js 4.1.0 4.1.0
postcss-nested 6.2.0 6.2.0

Moved: 5 · unchanged at every release: 17

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.