Pico CSS has ended maintenance, with v2.1.1 designated its final release. Creator Lucas Larroche announced the decision on October 4, 2026, and GitHub records the repository as archived that day. Developers can keep using the framework, but future fixes will need to come from elsewhere.
The announcement is several weeks old. Its practical consequence remains relevant to anyone choosing dependencies: the maintainer says package distribution and documentation will remain available, while upstream development has stopped.
What stays available
Pico is a CSS framework for semantic HTML. Its repository documentation describes a starting point for small projects, with a classless variant that styles ordinary HTML elements. Larger projects still require CSS or SCSS knowledge, according to its stated limitations.
The quick-start documentation continues to describe manual installation, a jsDelivr stylesheet link and package-manager options through npm or Composer. Those are documented distribution routes; this article does not test installation or rendered output.
In the maintenance notice, Larroche says npm, jsDelivr and picocss.com will stay online for the long term. He also closes the door on new issues, pull requests and releases. Availability therefore gives existing users a way to obtain the code, without a commitment to fix future problems.
Who owns the next fix?
For an existing site, the archived status alone doesn't establish a need for an immediate redesign. A useful response is to record the version in use and decide who would handle a browser regression or accessibility defect. The repository's browser-support statement describes testing against current stable browsers, but an archived project cannot keep renewing that assurance through releases.
For a new project, that maintenance responsibility belongs in the dependency decision from the start. Keeping a copy of a stylesheet is straightforward; accepting responsibility for its future behavior requires an explicit choice.
The notice permits forks under the MIT licence, while excluding the Pico CSS name and logo and asking forks to use their own names. Developers considering a successor should watch for actual maintenance: documented fixes and evidence of browser testing. Forking permission makes continuation possible. It doesn't establish that a particular successor is ready to maintain your site.