Pico CSS was archived by its maintainer on October 4, 2026. v2.1.1 is the final release, forever. If your project runs on Pico, nobody is patching it anymore.
I build small devtools in the open, and this one, picoexit , answers the question every Pico user now has to answer: what exactly am I depending on, and what do I do about it?
Measure before you migrate
The biggest mistake in any framework migration is starting to rewrite before you know what you have. picoexit audit scans your HTML, CSS and JS for real Pico usage:
node dist/src/cli.js audit ./my-site
# picoexit audit - Pico delivery: ** cdn ** ( v2.1.1 ) - Pico selectors used: ** 45 distinct ** , 85 occurrences
## Drift-risk selectors - ** role = search ** ( high risk ) : Pico styles [ role = search] focus behavior with :has () selectors ; core behavior, not just decoration. - index.html:29
Enter fullscreen mode
Exit fullscreen mode
On my sample site it found 45 distinct selectors across 85 occurrences, each with a drift-risk flag.…