drops

uuid ひとつで、機能が降ってくる。

A drop is one feature for noraneko: a small signed xpi, built by a registry from source that sits in the open, and read by you before anything runs. The uuid is what a drop is; the name is only its label.

the catalogue is at noraneko.f3liz.casa/drops/ · registry: f3liz-casa/noraneko-registry · since September 2026

how a drop reaches you

Open a drop's page in the catalogue inside noraneko and press install. It is a plain link to the xpi, the way "Add to Firefox" is; noraneko catches it and opens its settings with the uuid. There it downloads the xpi, checks the sha256 and the registry's signature, and shows you the source and every file that would run. Nothing runs until you press install there. In another browser, copy the uuid and paste it into about:nora:settings.

Installing does not need a restart, and "put back" returns the built-in. A drop is installed as a temporary add-on and put back in place at every start from the xpi you already read.

the shape

A drop is an actor: one TypeScript file that says what runs in the main process and what runs on the page, the same shape Firefox uses for its own new tab. The xpi is only the envelope.

the registry

The registry is a git repository. A drop is a folder with a drop.toml (uuid, name, note, contact) and its source. The author opens a pull request; a person reads it; when it is merged the registry's CI builds the xpi from that source, reproducibly, signs the manifest with keyless Sigstore under the registry's own identity, and posts it to the server that serves it. The author never uploads a binary, and the server writes nothing that is not signed by the registry.

So the trust is: the registry's main branch, and whoever reviews it. noraneko keeps a list of registries (this one is the default) and you can add your own; fork the repository, point it at your own server, and it is a registry. Names are per registry; the uuid is what stays the same everywhere.

what you see before saying yes

the registry's signature, and a link to its Rekor entry
who wrote it, as a contact you can reach
the source as written, and every file that would actually run
which pages it runs on, and what it can call in the main process

what it is not

not an add-on store. There is no account, no rating, no automatic update; a new version is a new xpi you read again
not a sandbox yet. A drop runs with the browser's privileges; that is why the reading comes first. Narrowing what a drop can touch is the next piece of work
not a promise from the registry. Its signature says "this was built from that source, after review", nothing more

go

Drafted by Shiro, an AI assistant, sitting next to nyanrus. If something here is a misreading, please say so.