mrkeyoor.comAsk

foundation/yetitested 03 Oct 2026commit 4577f24

yeti review

Keep Yeti on a pinned evaluation track until its artifact status is clear and you have reproduced the test outcome.

  • Build 6 s
  • Tests failed
7 sto install
  • 14 packages
Webevaluationupdated 01 Nov 2026
+5stars / 7d

Evaluate Yeti for a new site whose browser requirements match Baseline 2025, but keep adoption provisional until you have checked its release status and reproduced its tests. Yeti is Foundation's CSS-first successor to Foundation for Sites, with named layouts, a shared token system and optional JavaScript modules. Its installation guide says there is no npm package or download yet. Our run on October 3, 2026, at commit 4577f24 installed successfully and built successfully, but the test command failed.

Verdict

Keep Yeti on a pinned evaluation track until its artifact status is clear and you have reproduced the test outcome. In our run on October 3, 2026, at commit 4577f24, installation took 7 seconds, the build took 6 seconds, and the test command failed after 9 seconds. That supports a source-build trial for a site targeting Baseline 2025, with browser behavior and deployment still to verify.

We ran it

Lab card: what happened when we ran yeti
Lab card from our sandbox run
Screenshot of yeti (foundationcss.com)
foundationcss.com
Install✓ · 7s14 packages · 44 MB
Build✓ · 6s
Tests✗ · 9sran, no count parsed
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo640 files~14,219 lines of source · 8.4 MB · 1 CI workflows · tests dir

Answers from our run

Does yeti build from source?

Dependencies installed in 7 seconds (14 packages), and the build succeeded in 6 seconds. We cloned commit 4577f24 into a clean Debian container with 3 CPUs and no project-specific setup.

Do yeti's tests pass?

No. The project's own test command exited unsuccessfully after 9 seconds, and its output did not expose an individual test count.

Does yeti have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use yeti?

Teams that require a released npm artifact: the supplied installation guide explicitly says none is available yet.

What are the alternatives to yeti?

Pico CSS, Bootstrap, Tailwind CSS. Keep Yeti on a pinned evaluation track until its artifact status is clear and you have reproduced the test outcome.

Setup3/5Basic setup worked: installation took 7 seconds and compilation succeeded. Early evaluation still requires a source build according to the installation guide.
Docs4/5Detailed installation and stability guidance earns 4 under the visible rubric, with release-status conflicts and a failed guide-render check as explicit caveats.
Community4/5This assesses documented support routes: Discussions, issue templates and contribution guidance. Response quality, active contributor numbers and Yeti-specific adoption were not measured.
Maturity2/5Substantial readiness limits remain: supplied release descriptions disagree and the recorded test command exited 1 on a missing guide file.

Who it’s for

Designers evaluating named layouts and data attributes for a new site targeting Baseline 2025.
Teams that want to consume a stylesheet without requiring Sass, Node or a bundler in their site.
Foundation users prepared to evaluate a successor separately from their existing version 6 application.
Tool authors interested in the documented manifest, editor completion data and generated assistant documentation.

Who it’s NOT for

Teams that require a released npm artifact: the supplied installation guide explicitly says none is available yet.
Sites that must support browsers older than Baseline 2025.
Teams requiring a passing repository test command before evaluation can proceed.
Vendors requiring immediate MIT terms for a competing product: Yeti uses FSL-1.1-MIT, with each release converting to MIT two years after shipping.

Setup reality

Our run on October 3, 2026, used commit 4577f24 in our sandbox, recorded as lab-node:22 with 3 CPUs and 8 GB of memory. Installation succeeded in 7 seconds. The build succeeded in 6 seconds. The test command exited 1 after 9 seconds; its log identifies a guide-render check that could not open /work/repo/docs/guides/markup.md.

The harness stores command success, exit status, elapsed time, timeout status and log tails separately. These outcomes establish repository installation and compilation in that sandbox. They do not establish successful browser interaction, accessibility, deployment or production performance. This correction uses the existing record and includes no new execution.

The stored dependency measurement is 14 packages occupying 44 MB. Separately, the installation log says it added 11 packages and audited 12; those log figures do not replace the stored measurement. npm audit recorded zero advisories, but scan coverage is unknown because the record has no scannedPackages field. This was not a security review.

For an early evaluation, the installation guide directs readers to clone the repository and build dist/. Its package paths describe an intended release workflow, not evidence that a package is available.

Should you adopt Yeti now?

Use a pinned evaluation to decide whether Yeti's layout model fits your site. The supplied README describes a stylesheet that consumers can use without Sass, Node or a bundler. The installation guide, however, says Yeti has not been released and directs early testers to build from the repository. That distinction matters when choosing between trying the design system and making it a team dependency.

Our run on October 3, 2026, at commit 4577f24 installed successfully and built successfully, but the test command failed. Treat that result as a reason to investigate the snapshot before committing to it.

What our sandbox established

Installation succeeded in 7 seconds. The build succeeded in 6 seconds. Tests exited 1 after 9 seconds, without timing out. The build log reports that it wrote dist/; it does not demonstrate that we deployed a site or exercised its components in a browser.

The named failure was the check that every guide under docs/ is a fresh render of its source. It attempted to read /work/repo/docs/guides/markup.md and received ENOENT. The supplied tail does not establish whether generating documentation, restoring a file or changing the test reference would resolve it. It also does not establish that browser or screenshot suites completed.

The attached aggregate test-count field is null. The raw tools-suite footer contains its own counts, but those are not an exhaustive count of unique tests across the repository. We therefore make no aggregate passing-test claim.

Our harness records each command's outcome, exit code, elapsed time and timeout status, with a log tail for context. The MrKeyoor testing methodology explains this approach and its limits. That page was supplied in its November 1, 2026 form; it is background on provenance, not proof that the October run used every detail of today's procedure.

What you get from the stylesheet

Yeti uses named layout primitives configured through classes and data attributes. Its README describes container queries, cascade layers and native nesting as parts of the implementation. A shared token scale controls typography and spacing.

The installation guide distinguishes the base stylesheet from optional component modules. Modules add behavior such as tab focus movement, dialog focus return and form validation messages. Those are documented capabilities, not browser behaviors verified by our run. The README's accessibility claims likewise remain maintainer claims here.

The same guide describes editor completion data and generated manifest documentation. It also gives a practical limitation: editor formats cannot restrict an attribute suggestion to the component class that accepts it. Authors still need to check whether an attribute belongs on a particular element.

Check release status before following package examples

The supplied README labels Yeti 7.0.0-beta, while our recorded build log identifies yeti-css@7.0.0-alpha.0. The installation guide says no release, npm package or download is available yet, and explicitly says its later instructions describe how installation will work after release. These sources do not provide one consistent release state.

The stability guide promises that specified public names are frozen from 7.0.0-beta.0. It also says token defaults, generated-file internals, test fixtures and browser minimums may still change. A promise about public names does not resolve artifact availability or the failure observed in our sandbox.

Before adopting, confirm which artifact and version you will consume, reproduce the guide failure at the pinned commit, and evaluate the components your own pages require in your supported browsers.

Browser and license requirements can rule it out

Yeti targets Baseline 2025 and provides no polyfills for older browsers. Check that floor against your actual browser requirements before spending time on a trial.

Yeti's README identifies its license as FSL-1.1-MIT. It permits use, modification and redistribution except for offering a competing product; each release becomes MIT two years after it ships. Foundation for Sites 6 remains MIT and continues on the v6 branch. Existing Foundation users should evaluate Yeti as a successor rather than assume the current branch is an ordinary version 6 update.

Alternatives answer different needs

Pico CSS offers semantic HTML styling, but its repository is archived and v2.1.1 is its final release. Consider it only if a fixed, unmaintained starting point is acceptable. It should not be recommended as an actively maintained escape from Yeti's release uncertainty.

Bootstrap provides compiled CSS and JavaScript, but its supplied default-branch README describes Bootstrap 6 development and points Bootstrap 5 users to v5-dev. Compare the version you intend to use rather than treating the default branch as a stable production release.

Tailwind CSS describes itself as a utility-first framework for custom interfaces. It is a replacement styling approach to consider when your team prefers utilities; the supplied extract does not establish build requirements, browser compatibility or ecosystem size.

These are choices for a site's styling foundation. The supplied evidence does not establish that combining them with Yeti would be useful or conflict-free.

How to read our ratings

Scores describe the supplied evidence for this evaluation, not adoption or popularity. The rubric is: 1 means a documented obstacle prevents the basic task; 2 means substantial readiness limits remain; 3 means basic setup works with unresolved friction; 4 means detailed guidance or established support routes are available, with specific caveats; 5 requires evidence of consistent readiness beyond this single run. Community measures available support and contribution routes, not user numbers or response quality.

Setup ease is 3 because installation and compilation succeeded, while early users still need a source build. Documentation is 4 because the supplied guides explain installation, optional modules, tooling and stability, despite conflicting release descriptions and the failed guide check. Community is 4 for the documented Discussions, issue templates and contribution route; responsiveness and Yeti-specific adoption remain unmeasured. Maturity is 2 because release descriptions conflict and our test command failed.

Alternatives

ProjectWhat it isPick it when
Pico CSSA semantic HTML styling framework whose repository is archived and whose final release is v2.1.1.Choose it for a minimal starting point only when accepting an unmaintained dependency is an explicit decision.
Bootstrap gh↗A frontend framework providing compiled CSS and JavaScript; its supplied default branch is for Bootstrap 6 development.Consider it when you want its compiled assets, after selecting the intended version and checking that version's documentation.
Tailwind CSS gh↗A utility-first CSS framework for building custom interfaces.Consider it when utility classes match how your team wants to author styles; assess compatibility and installation separately.

What people are saying

  1. [velocity-scout] foundation/yeti
  2. [theverge] Logitech’s new Blue Yeti 2 mic adjusts itself to where you are

Sources

  1. Yeti repository and README
  2. Installing Yeti
  3. Yeti stability guide
  4. Yeti license
  5. Foundation for Sites is becoming Yeti
  6. Foundation v6.9.0 release

More web reviews