Questions people actually ask

Every submitted version runs through the same pipeline: the archive digest, the manifest against the components really present, automated rules over the source, the dependency list, a malware lookup, an isolated run with no network, and a semantic comparison between what the code does and what was declared.

A single critical finding rejects the version outright. Anything ambiguous goes to a person. Nothing is published because no rule happened to fire. The full policy is here.

It means what it says and nothing more: at the moment it was reviewed, that exact archive passed those checks, and the record is published with it so you can read what was and was not verified.

Stages that are not configured are marked skipped, never “passed”. Files the analyser could not read are declared rather than ignored. A plugin still runs with your permissions — read what it asks for.

One. The same machine can start the plugin as often as it likes; a second machine is refused.

Changing computer does not need a support request: from your account you release the licence and activate it elsewhere. The machine that was using it stops working. That is limited to three times every thirty days.

It stops working, including for you. Suspension exists to pull something found harmful after publication, and a suspension that spared people who had paid would protect nobody.

It takes effect at the next licence check, and within twelve hours on a machine that had already checked in — a plugin is allowed to keep running for that long on its last answer, so that our own downtime does not stop plugins that are perfectly fine. That window is the price of not having your work depend on our uptime.

If a plugin you bought is withdrawn, get in touch: depending on when you bought it and why it was pulled, a refund may be due.

Nothing stops you copying files you already have — they are files. What you would lose is updates, the digest check that proves the bytes are the reviewed ones, and any plugin that verifies its licence at startup.

A renewal extends from the end of the period you already paid for, never from the day the payment lands — paying early does not shorten what you bought.

Cancelling stops the next renewal and nothing else: access runs to the end of the period you paid for. Access also survives 3 days past the renewal date, so a late payment notification cannot lock you out of something you have paid for.

Yes, under the conditions on the refunds page. Worth knowing up front: a refund revokes the licence immediately. The plugin stops working as soon as the refund is recorded, not at the end of a period.

Not automatically — the platform records orders, it does not issue tax documents yet. If you need one, ask.

30% on the first €10.00, 15% on anything above, applied band by band rather than all-or-nothing. On €4 that is 30%, on €12 it is 27.5%, on €50 it is 18%.

Raising your price is therefore never worth less to you: each extra euro is only ever charged the lower rate. The higher rate on the first slice covers what does not scale with price — the card fee is a fixed amount per transaction, and every version you submit runs in a sandboxed container whatever it sells for.

Earnings accumulate as buyers pay. Once your balance passes €25.00 it is settled to the account in your publisher settings — below that it carries forward, because a transfer of a few euros costs more than it moves.

Add your IBAN before your first payout: without it there is no way to send what you are owed.

The version page lists every finding with the file and line that triggered it, and the rule id behind it. Fix what it points at and submit a new version.

If you believe a finding is wrong, say so — rejected versions stay in the review queue precisely so a person can take a second look at false positives.

Yes. A licence is for the plugin, not for one version: buyers get every approved version. Each new version goes through the full review again — being published once does not exempt what comes next.

New purchases use the new price. Existing subscribers keep the price they signed up at; changing what an active subscriber pays would need their agreement.