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.

  1. An author puts drops/<name>/drop.toml (uuid, name, note, contact, actors) and drops/<name>/src/<actor>/actor.ts in a PR. The PR's diff is exactly "the source that becomes the xpi," so the review reads it. The identity is the uuid (one from uuidgen; once set, never changed); name is 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.
  2. CI builds with tooling/ (the build tools vendored from noraneko, pinned by commit) — reproducibly.
  3. A person reviews it (the gate is a PR review against this repo's main).
  4. Once it lands on main, CI builds, copies the contact into the manifest, presses a keyless signature onto manifest.json under the registry's identity, and POSTs it together with the xpi to dl.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.json carries the Rekor and run links. The manifest's source is "this registry, this commit, drops/<name>/src," and the source is bundled inside the xpi too.
  5. 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>

Learn more