noraneko-registry
The ledger of noraneko's drops — features that fall from a single piece of code. A drop is an xpi (a container) plus a JSWindowActor, the same shape as Firefox's own about:newtab. What we put first is not "someone signed it, so install it" but "the person installing can read what's inside." The signatures here are testimony, not a gatekeeper.
Shape
Everything stays inside the registry. The drop's source itself lives here; the build happens here; the signature is made here. No outside repo is used.
- An author puts
drops/<name>/drop.toml(uuid, name, note, contact, actors) anddrops/<name>/src/<actor>/actor.tsin a PR. The PR's diff is exactly "the source that becomes the xpi," so the review reads it. The identity is theuuid(one fromuuidgen; once set, never changed);nameis the label (the same as the dir; unique within this registry). Same picture as Julia's General: the same name in another registry is a different thing if the uuid differs. - CI builds with
tooling/(the build tools vendored from noraneko, pinned by commit) — reproducibly. - A person reviews it (the gate is a PR review against this repo's main).
- Once it lands on main, CI builds, copies the contact into the manifest, presses a keyless signature onto
manifest.jsonunder the registry's identity, and POSTs it together with the xpi todl.f3liz.casa/drop/<uuid>. The receiving side (a Cloudflare Worker) verifies that signature, the xpi's sha256, and the uuid before writing to B2, and on the way out returns only what the signature passes. This repo holds no B2 key (the signature itself is the gate).attestations.jsoncarries the Rekor and run links. The manifest'ssourceis "this registry, this commit,drops/<name>/src," and the source is bundled inside the xpi too. - The browser (noraneko) holds a list of registries (this repo by default; you can add and remove them in settings — the same picture as alternative app stores on iOS). Enter a uuid (it asks the registries in the list in order and downloads from the first that has it), and it checks the integrity (sha256) and "is it signed under that registry's identity," then shows the permission sheet, the source, the files that will actually run, and the contact. Green if it all lines up, red if not (it does not stop you). Then you decide to install.
Locally
mise install
npm install
mise exec -- ruby scripts/dev.rb drops/<name> # the loop while writing (watch, build, put on the shelf)
mise exec -- ruby scripts/build.rb drops/<name> # build once. xpi and manifest in _build/<name>/
node scripts/verify.mjs drops/<name>/manifest.json.sigstore.json drops/<name>/manifest.json <registry identity>
scripts/dev.rb: watchesdrops/<name>/and the shell, rebuilds withbuild.rb --devon change, and puts it on your local shelf withshelf.rb.--devadds a fourth number to the version (the rebuild mark), so the same version never changes bytes underneath you — you can see it without rebuilding the browser. CI does not pass this flag (the reproducibility promise stands).scripts/build.rb: laystooling/webext-actorsanddrops/<name>/srcout in_stage/, builds, and turns it into an xpi withscripts/build-drop.rb. The steps you can trace by hand are indocs/BUILD.md; the traps we hit are indocs/TRAPS.md. If you are making your first drop, readdocs/GUIDE.md. How things are placed (the promise that removal restores what was there) and the layers, dependencies, and compat are indocs/LAYERS.md. The table of what a drop is allowed to do (permission / effect / fact) isdocs/ABI.md. Whatstdbrings and the words your logic writes with isdocs/STD.md.docs/language.mdanddocs/for-drops.mdin nyanrus/tsubaki are the language side: the same Tsubaki a drop's logic is written in, at the depth a drop needs (state, action,view, effects).scripts/verify.mjs: the official@sigstore/verify(Node). Down to Fulcio's chain, Rekor v1/v2, TSA, and SCT.- The verifier inside the browser is
@freedomofpress/sigstore-browser(noraneko'smodules/sigstore/).
Learn more
- Your first drop: GUIDE — where things go, the smallest Tsubaki, running it locally, publishing
- What lives where: LAYOUT — drop locations, build artifacts, what the browser holds
- Signatures, and who decides: TRUST — the root of trust, the PR gate, the reproducibility promise
- Build by hand: BUILD / Layers and cleanup: LAYERS
- Connect the local shelf: SHELF / Traps: TRAPS