PUBLISH
Review
When you run kiri plugin publish, your plugin isn’t listed straight away. The marketplace, which lives in Kiri Cloud, checks every upload automatically, and a person looks as well the first time a plugin is listed and whenever an update asks for more than the version before it. Review is there so that the install prompt people read is true. It doesn’t decide whether your idea is good.
From publish to listed
kiri plugin publish runs kiri plugin check and kiri plugin test on your computer before it uploads anything, so most problems stop there, where they’re quickest to fix. What reaches the marketplace has already built, passed its own tests and been signed. See Test and publish.
The automatic checks
Five checks run on every upload, in order. The first one that fails stops the rest, and kiri plugin publish prints which one and why.
| Check | What it looks for | How to pass |
|---|---|---|
| The signature | The upload is signed with one of the publisher’s keys, and publisher in kiri-plugin.toml is that publisher. |
Publish with a key made by kiri plugin key create on your account. From CI, use the key --for-ci printed, kept as KIRI_PLUGIN_KEY. |
| The files | Only the plugin: the WebAssembly or the container image, kiri-plugin.toml, the lang folder and the listing folder. |
Build with kiri plugin build or publish, which pack only those. Nothing else in the folder is uploaded. |
| The permissions | The lines this version’s prompt would show, compared with the version before. | The same or fewer: nothing to do. More: the version waits for a person, then asks everyone who has the plugin before it installs. |
| The scan | Known problems in the plugin’s code and, for a container plugin, in its image. | Keep your packages and base image up to date. The scan names each problem and the version that fixes it. |
| A test start | The plugin starts in a box, says hello, and registers only handlers its file lists. A container plugin has an image for both arm64 and amd64. | Run kiri plugin dev and kiri plugin check first; both catch a handler the file doesn’t list. kiri plugin build builds a container plugin for both chips. |
$ kiri plugin publish
acme-status 1.1.0 by acme
✓ check
✓ test: 6 passed
✓ built sha256:7b20e4c9a1f3… · WebAssembly 640 KB
✓ signed with key "ci" (added 12 Nov 2026)
✓ uploaded
Automatic checks
✓ signature matches the publisher
✓ files: nothing outside the plugin
✓ scanned: no known problems
✓ started in a box and said hello
! permissions: 1.1.0 asks for more than 1.0.0
+ Reach these websites: status.example.com
Waiting for review. 1.0.0 stays listed until 1.1.0 is.When a person looks
A person reviews a plugin twice in its life, at most: the first time it’s listed, and for each update whose prompt has a line the version before didn’t. Every other upload is listed as soon as the automatic checks pass, in minutes.
The reviewer reads what the person installing it will read, and checks that it’s true:
- The prompt fits the plugin. Each permission line has a reason in what the plugin does. A scanner that asks to start and stop containers, or a note that asks to reach ten websites, gets asked why.
- The listing is honest. The name, mark, description and screenshots say what the plugin is, and don’t pass it off as part of Kiri or as another maker’s plugin.
- Settings ask for the right thing. An address field with
reach = trueis for a server only the person knows. A secret has aforthat points at the one site it belongs to, anduse = "program"only when a program must read the key itself. - It does what it says. The reviewer installs it, uses its places, and reads its activity record.
Automatic checks take minutes. A person takes longer. While a version waits, it isn’t offered to anyone, and the version before stays listed and installed.
When something fails
Nothing is listed until everything passes. A failure, automatic or from a person, comes back to you with the reason in plain words, in the output of kiri plugin publish and on your publisher account. Fix it and publish again: the version number isn’t used up by a failed upload, so you can publish the same version once more.
Ranks
Every listing shows who made the plugin, as one of three ranks:
| Rank | Means |
|---|---|
| Kiri | Made by Kiri, such as the Trivy scanner. |
| Verified | Kiri checked the publisher’s name and company. |
| Community | Listed by its publisher. Every new publisher starts here. |
A rank says who made the plugin, never that it’s safe. The install prompt and the gate do that, whatever the rank: a Verified plugin can do no more than its prompt lists, and a Community one no less. The marketplace keeps a copy of every version it lists, so a version can’t change after it’s listed.
Taking a version back
If a version is wrong, withdraw it:
kiri plugin publish --withdraw 1.2.0 --reason "Blocks digests by mistake. 1.2.1 fixes it."
Nobody can install a withdrawn version any more. Computers that have it go back to the version before at their next daily check, and show a notice with your reason. The version number stays used, so the fix goes out as a new one, and it goes through the same checks.
If a plugin turns out to be harmful, Kiri can take it off the marketplace itself. Every computer that has it switches it off at its next check and says why.
© 2026 Kiri · The SDK is open source under the Apache License 2.0 · Docs · runkiri.com