Write a YAML recipe, push it through the Hub CI, and your tool ends up signed in registry.biochef.app and runnable from the BioChef web app.
Quickstarts
Three ways in
Pick a path and get to a running BioChef in under five minutes.
Step 01 · Author
Write a new recipe
Author a YAML recipe in your own repo. The Hub workflow validates, signs, and publishes it for you.
1Fork biochef-recipes and create recipes/<tool>/biochef.yaml.
2Run hub validate on it. CI also runs each built tool on the example input of its data types, so declare the types carefully.
3Open a PR. The reusable Hub workflow runs validate → build → test → SBOM. After merge it publishes, signs with cosign, attaches SLSA provenance and republishes the signed catalogue.
Clone the SPA, install deps, and serve it with the dev server. No backend required.
1git clone https://github.com/ieeta-pt/biochef-app and npm install.
2(Optional) install Emscripten 3.1.65 and run npm run build-wasm to rebuild the SPA's bundled GTO modules from source. Hub CI uses Emscripten 4.0.18 for new recipes.
3npm start and open http://localhost:8082.
Or docker compose -f docker-compose.dev.yml up: the app plus an empty local registry. The tools profile adds the Hub to publish recipes into it.
Tools live in the BioChef Registry as content-addressable OCI bundles. The web app fetches them by digest at runtime; you can pull them with ORAS and verify them with cosign.
1Resolve a tool by digest in the signed index.json catalogue.
2Pull the OCI bundle (bundle.json + WASM/JS layers + SBOM) with ORAS.
3Verify the bundle's cosign signature and SLSA provenance; the web app itself checks the catalogue signature and every digest before running it.