Skip to content
HN On Hacker News ↗

Pico CSS is no longer maintained · picocss/pico · Discussion #754

▲ 200 points • 111 comments • by henrid • 7d ago • HN discussion ↗

Pangram verdict · v3.3

We believe this text is mainly AI, with some human-written content.

91 %

AI likelihood · overall

AI
9% human-written 91% AI-generated
SEGMENTS · HUMAN 3 of 8
SEGMENTS · AI 5 of 8
WORD COUNT 199
PEAK AI % 100% · §3
Analyzed
Oct 30
backend: pangram/v3.3
Segments scanned
8 windows
avg 25 words each
Distribution
9 / 91%
human / AI fraction
Verdict
AI
Pangram v3.3

Article text · 199 words · 8 segments analyzed

Human AI-generated
§1 Human · 6%

v2.1.1 is the final release.

§2 AI · 100%

Why Today, AI can generate lightweight, standalone, accessible HTML with just the CSS it needs, so a Minimal CSS Framework for Semantic HTML matters less than it used to.

§3 AI · 100%

To stay relevant, Pico CSS would need a full rewrite: plain modern CSS instead of Sass, built on features it doesn't use today (OKLCH colors, cascade layers, Popover, anchor positioning) with fallbacks for older browsers, and a native compiler that strips unused CSS and makes customization easy. That would be a different project. Pico CSS stays as it is. What this means Nothing breaks. npm, the jsDelivr CDN and picocss.com stay online for the long term.

§4 AI · 100%

The repositories are archived. No new issues, PRs or releases. Pico CSS is MIT licensed. You're free to fork it and take it further.

§5 Human · 3%

See community forks.

§6 Human · 2%

The Pico CSS name and logo are not covered by the MIT license.

§7 AI · 100%

Please give your fork its own name, so users don't confuse it with the original. Thank you What started as a small side project ended up powering thousands of websites.

§8 AI · 100%

Thank you to everyone who used it, opened issues, sent pull requests and wrote kind messages over the years.