Six CSS modules give you a baseline, not a finished interface
Pure's advertised 3.7 KB minified and compressed bundle covers the unglamorous parts of a new page: a Normalize.css base, fraction-based grids, forms, buttons, tables, and menus. The class names are readable. A row is pure-g; a half-width column is pure-u-1-2; a primary button is pure-button-primary. You can link the stylesheet from jsDelivr or take it from the npm package.
That small surface is Pure's point. It does not bring a theme engine, a JavaScript runtime, or an inventory of application widgets. The repository itself is similarly compact at 138 files, about 4,507 lines of source, and 2.9 MB checked out. Pure is easiest to understand as a prepared sheet of graph paper: the lines help you place the work, while the actual visual language still belongs to your project.
What happened when we ran it
Our sandbox installed commit 520f5ce in 10 seconds. npm added 501 packages, and the working environment occupied 201 MB after installation. That is a sizable contributor toolchain beside a stylesheet advertised at 3.7 KB, but it is development weight rather than CSS every visitor downloads. The repository had a tests directory and 4 CI workflow files, with no Dockerfile.
The build completed in 1 second, and the supplied tests passed in 4 seconds. npm audit found 0 known vulnerabilities across critical, high, moderate, and low severity. We ran those commands in an unprivileged Debian container with 3 CPUs, 8 GB of RAM, and no secrets. The result covers installability and repository checks. It says nothing about page performance or visual correctness in your product.
One detail deserves attention before contributing. The current README says source builds need Node.js 26 or newer and npm 12 or newer. Our measured image was named lab-node:22, yet install, build, and tests all succeeded at commit 520f5ce. Treat the documented versions as the supported path, even though our run shows the checked commit was less strict in practice.
The 3.7 KB headline leaves responsive grids in a second file
The main rollup does not include responsive grid media queries. Pure's start guide tells you to load grids-responsive-min.css separately, then add classes such as pure-u-md-1-2 or pure-u-lg-1-4. Without that file, a pure-u-1-3 column stays one third wide regardless of the viewport. This is easy to miss if the bundle-size line is the only part of the README you remember.
The default responsive sheet starts its named breakpoints at 568 px and continues through larger desktop sizes. You can generate custom fractions and media queries through the package's generateGrids() function. Release v3.1.0 moved that generator into Pure itself after removing the older Rework-based tooling. That is useful for a small design system that wants Pure's grid syntax without accepting every built-in breakpoint.
Menus need your JavaScript when behavior matters
Pure can style horizontal, vertical, dropdown, and scrollable menus. It does not pretend that CSS alone completes an accessible navigation component. The menu documentation recommends JavaScript for submenus and provides an example with ARIA support, limited arrow-key handling, outside-click dismissal, and Escape-key dismissal. It also says a production team may need fuller keyboard navigation and edge detection.
There are sharper boundaries. Dropdowns are unsupported in the scrollable horizontal menu, and submenus are unsupported in the scrollable vertical menu. Those limits are good reasons to choose Bootstrap or a dedicated accessible component library when navigation is central to the product. Pure works better when menus are simple or when your team already owns the behavior layer.
v3.1.0 changes the workshop while leaving the CSS alone
Pure was pushed on September 29, 2026, one day after v3.1.0 shipped. GitHub showed 23,725 stars and 0 combined open issues and pull requests. Recent work closed old documentation and accessibility reports, replaced the deprecated Grunt build with ESM npm scripts, removed Rework, and moved npm releases to GitHub Actions with provenance. The dates and closed queue point to active maintenance rather than a dormant package with a fresh tag.
The release notes make an equally important promise: apart from comments and a license link in the banner, v3.1.0's CSS is unchanged from v3.0.0. That is a mature-project decision. Maintainers modernized the machinery around the output instead of making downstream sites absorb a redesign. The README limits browser testing to current stable Firefox, Chrome, and Safari, so teams with older-browser contracts still need their own matrix.
Pure earns its place when your team wants to own the last mile
The lab result is reassuring: 501 packages installed, a 1-second build passed, a 4-second test step passed, and the audit returned 0 known vulnerabilities. The bigger decision has little to do with setup. Pure supplies clean CSS primitives and then gets out of the way. That freedom is productive for a brochure site, documentation surface, server-rendered app, or handcrafted interface with an established design direction.
It is a poor bargain when the team is really shopping for finished components. You will write the modal, disclosure, validation flow, responsive navigation behavior, and the product's spacing and color rules. If that work is already yours, Pure keeps the dependency quiet. If you want the framework to make those decisions, start with Bootstrap, Tailwind plus a component library, or Pico instead.