blake3

utilities ยท ready ยท Rust, WASM

blake3 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 uses it

The stack repos that declare a dependency on it. A breaking change has to be carried through each of them, and through any consumer that no manifest declares. Only the stack's own projects are listed, so a consumer outside the stack is not here.

Used byKindDeclared inThrough
zzz runtimepackage.json@fuzdev/blake3-wasm
fuz_app peerpackage.json@fuzdev/blake3-wasm
gro peerpackage.json@fuzdev/blake3-wasm
fuz_util optional peerpackage.json@fuzdev/blake3-wasm
corpora devpackage.json@fuzdev/blake3-wasm
fuz-stack (docs.fuz.dev)devpackage.json@fuzdev/blake3-wasm
fuz_blog devpackage.json@fuzdev/blake3-wasm
fuz_code devpackage.json@fuzdev/blake3-wasm
fuz_css devpackage.json@fuzdev/blake3-wasm
fuz_forge devpackage.json@fuzdev/blake3-wasm
fuz_repos devpackage.json@fuzdev/blake3-wasm
fuz_schema devpackage.json@fuzdev/blake3-wasm
fuz_template devpackage.json@fuzdev/blake3-wasm
fuz_ui devpackage.json@fuzdev/blake3-wasm
mdz devpackage.json@fuzdev/blake3-wasm
svelte-docinfo devpackage.json@fuzdev/blake3-wasm
tsv devpackage.json@fuzdev/blake3-wasm
tsv (tsv.fuz.dev)devpackage.json@fuzdev/blake3-wasm
zap devpackage.json@fuzdev/blake3-wasm

What it uses

UsesKindDeclared inThrough
fuz_schema devpackage.json@fuzdev/fuz_schema
fuz_util devpackage.json@fuzdev/fuz_util
gro devpackage.json@fuzdev/gro
tsv devpackage.json@fuzdev/tsv

Read from the repos' manifests on . Only each repo's root manifests are read. A manifest shows what a repo declares, which is not always what its code imports, and a dependency that no manifest states, such as a sibling checkout a test reads, is not here. The kind is the manifest table a dependency is declared in, not how much it matters: an app that bundles what it builds declares everything as dev. See every dependency in the stack.

What it declares from outside the stack

runtime
Cargo.toml: blake3, serde, serde_json, wasm-bindgen, wasmtime, wasmtime-wasi, wit-bindgen

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

The check script of its package.json:

npm run typecheck && npm run test:rust && npm run test:tooling && npm run lint && npm run lint:docs && cargo fmt --all --check && tsv format --check .

How its CLAUDE.md comments its check command:

  • npm run check  # typecheck (cargo + tsc) + test:rust + test:tooling + clippy + rustdoc + fmt
    line 14
  • npm run check  # Full check (typecheck + test:rust + test:tooling + clippy + rustdoc + cargo fmt --all + tsv format --check)
    line 186

It is among the repos with a Cargo workspace at the root; with no CI workflow.

It has no CI workflow.

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

Comparisons that name it

ComparedAgainstKindRunsSource
blake3 WebAssembly buildsThe native blake3 crate's test vectorsReference
Release: the publish steps
On demand: by hand
test vectors

From Oracles in use.

Gates

  • blake3 has no CI, so its size limits and test vectors run only by hand and before a release

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.

Actions kept with a person

  • Publish a package (permission rule, dry run by default, written rule): The harness denies the publish commands, in settings that are not public. The release scripts of tsv, pglet and blake3 change nothing without an explicit flag, which a session could pass. The publish task of gro and the release task of fuz_forge have no such default.

From Actions kept with a person.

Values

  • A decision: size over speed. A second build without SIMD, about 30% smaller, for where bundle size matters more. Cost: In that build, the two to three times SIMD gains on large inputs. install

From the values page.