Plugins, micro packs and themes for rich

Every package in the rs-rich plugin marketplace, with the command that installs it. In a terminal, rich plugin search and rich plugin browse show the same list.

Packages

How to read a package

Which packages are rs-rich's own. A package marked โœ“ Official ยท by rs-rich is built and published by rs-rich, from its repository. The mark comes only from the listing's tier, which only a maintainer can set, and the marketplace refuses official for a package whose repository is not rs-rich's. Every other package is someone else's: Approved means a maintainer read its source and rebuilt the same file; Community means the marketplace's checks passed and nothing more, so read its source and permissions first. A package's own name, description and authors are its author's words; "Authored by" names them in quotes when they claim to be rs-rich. โ˜… Recommended is a maintainer's pick, with a note saying why. The tiers say more.

Kinds. A WASM plugin runs in a sandbox with no files, network, clock or processes. A micro pack and a theme are data. A crate is native code: it is never installed by rich, so its command is the cargo add line for your own program.

Trust

This page only lists packages. It reads this site's copy of the marketplace's index.json and each listing it names, checks each listing's SHA-256 against the index, and sends nothing anywhere. It does not check the index's signature. rich plugin install does: it verifies the minisign signature with the keys compiled into rich (the public halves are in keys/), then the listing's hash, then the downloaded file's size and SHA-256, before it writes anything.

Download counts and ratings come from the marketplace's stats.json, refreshed nightly. They are not part of the signed index, and rich never reads them to install anything. A rating is the ๐Ÿ‘ and ๐Ÿ‘Ž reactions on the package's discussion in the marketplace's Reviews category, and its reviews are that discussion's comments. A count shows as "โ€”" where nothing was counted, such as a version published before counting began.

In the terminal

rich plugin search                          # every package: kind, tier, version, author
rich plugin search rot13                    # every word must match
rich plugin search --kind theme --tier official
rich plugin info textcase                   # who publishes it, every version, permissions
rich plugin install textcase                # shows what it is and asks first
rich plugin browse                          # all of it in a selector

The rs-rich documentation has every rich plugin command, and the repository's README says how to publish a package.