Kit MarketplaceSign in with GitHub

What we review

Every version of every plugin is read by a person before it's listed. This is what they look for, and what gets a plugin taken down.

Before a person reads it

Kit’s checks run on every version, and one that fails is refused when you send it:

  • The kit-code.json is valid, as Kit checks it.
  • Its code loads in Kit’s sandbox, within 500 ms, and sets every hook, formula and kind of property it declares.
  • Its pictures are WebP, PNG or JPEG files sent with it, 2 MB each, each with words saying what it shows.

What the reviewer reads

  • All of its code. It must do what its readme and description say, and nothing else.
  • What it asks for. A plugin that only reads rows asks to read them; one that changes them says why, in asks.why.
  • Its page. The readme explains what it does and how to use it. The pictures show this plugin, at work.
  • That it’s yours. It isn’t a copy of someone else’s plugin, and doesn’t use another person’s or company’s name.

What gets changes asked for

  • It asks for more than its code uses, or less.
  • Its readme is missing, or doesn’t say what it does.
  • Its code is hard to read on purpose (packed, encoded, or built from text).

What gets it turned down, or taken down

  • It does something it doesn’t say, or tries to reach past the sandbox.
  • It damages or hides people’s data.
  • It misleads people about what it is, or who made it.
  • It copies someone else’s work.

A plugin taken down leaves the marketplace at once. Its page says why, and Kits that read its link again are told why. Its publisher sees the reason on Your plugins. A publisher who keeps breaking these rules can’t publish any more.

Reporting a plugin

Every listed plugin has Report this plugin on its page. You don’t need to sign in, and a person reads every report.