CodeSampleX

Recordsnpmpostcss8.4.49tailwindcss/plugin

Change the conditions
Fixed
Package version8.4.49 Symboltailwindcss/plugin
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

tailwindcss/plugin @8.4.49alpine musl · x64 · node 22 · npm · node

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

Project observations
1 / 1
Contract verifications
3 / 3
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 3

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

Library Version Health Measured there Projects
nanoid 3.3.18 CHANGED Version changed, no linked failure contract passed 2 project-days
picocolors 1.1.1 PASS All observations passed contract passed 2 project-days
source-map-js 1.2.1 PASS All observations passed contract passed 2 project-days
tailwindcss 3.4.17 PASS All observations passed contract passed 3 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.

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.

Moved: 1 · unchanged at every release: 3

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.