zervo

apps and sites ยท experimental ยท Rust

zervo as this site sees it: what its repo's own files declare, and every record on the coherence and values pages that names it or links it. This page is computed and adds nothing of its own. For what the project is, see the Fuz stack page.

What it declares from outside the stack

runtime
Cargo.toml: raw-window-handle, servo, tracing, tracing-subscriber, winit

Read from the repo on . What a repo's manifests declare from outside the stack, by name and without versions. The dev tables are left out, so what an app bundles from its dev table is not here. For a Cargo workspace the list is every crate's together, and it is what is declared, not what a release build links. A crate is left out as tooling only when it is named xtask or testing_*, or the release audit marks it dev-only, so what a bench, debug or test-support crate under another name uses is listed with the rest. See everything the stack declares.

Its check script and CI

Its package.json has no check script. It has a Cargo workspace at its root.

Its CLAUDE.md has no line in a code block that gives gro check or npm run check with a # comment, and none whose comment says to run it before committing. It may describe its checks another way.

It is among the repos with a Cargo workspace at the root.

.github/workflows/check.yml runs on push (branches main), pull_request (branches **), workflow_dispatch

check on ubuntu-latest

  1. uses actions/checkout, pinned to a commit
  2. Install Rust
    rustup toolchain install --no-self-update
    rustup show active-toolchain
    rustfmt --version
  3. Format
    cargo fmt --check
  4. Scripts
    sh -n scripts/audit_daemon.sh
    sh -n scripts/servo_gap_sites.sh
    python3 -m py_compile scripts/strip_secure_proxy.py

Read from the repo on . A workflow's jobs and steps are as the file writes them: a step's command, or the action it uses without its version. An action's inputs, a matrix's values, permissions, environment and working directories are left out, and nothing here says which command is the gate. A line is quoted when it sits in a code block of the repo's CLAUDE.md, has a # comment after the command, and either is the command gro check or npm run check, or has a comment that says to run it before committing. A repo that describes its check command in a sentence or a list, or in another file, has no line here. Every file is read at the repo's main branch as the checkout last fetched it, so nothing uncommitted or unpushed is here. See every repo's checks.

Holds that name it

Gates

  • Format, lints as errors, tests and doc links (every change): Lint and test failures and broken doc links. Where: The Rust workspaces, less the CI gaps listed below, and less zervo, whose lints only warn and which checks no doc links.
  • zervo's CI builds and tests nothing, because its browser engine is too heavy to build on each push

From Gates. A gate is listed here when its row names the project or links its repo, or speaks of a class of repos that the snapshot puts this one in.