four steps

add
1
Open source, on public GitHub

Your plugin has a licence file (any open source licence) and lives in a public GitHub repository. nerd installs from no other host.

2
A manifest and a tag

Its plugin.json has version and min_nerd, and a release tag v<version> points at the commit you submit.

3
Check it yourself

Both must be clean: the check, then the trial in the sandbox.

nerd --plugin-check --catalog <folder>
nerd --plugin-trial <folder>
4
Open a pull request

Add or change plugins/<name>.json in the catalog repository. One plugin per pull request.

Open the catalog repository

the entry

plugins/name.json

One file per plugin, named after its manifest.

{ "title": "Big files", "summary": "Marks files over 1 MB in the tree and the tab.", "url": "https://github.com/you/nerd-bigfiles", "tag": "v1.2.0", "commit": "<the 40 characters the tag points at>", "version": "1.2.0", "risk": 0, "review": "checked" }

nerd installs exactly commit. risk is what nerd --plugin-check --json says; nerd recomputes it and refuses an entry that disagrees. Open the pull request with "review": "checked": the review sets the real mark, not you.

What happens next

The review runs. A plugin that only shows things gets the mark checked by itself; any other gets reviewed after the maintainer reads it. How review works.

Featured

Set by the catalog’s maintainer, not by you.