DocsAccount

Reviews, bugs and updates

Who can review a product or report a bug, what's public and what stays private, how bugs reach a fix, and how you hear about new versions.

Updated October 12, 2026This page as Markdown

Every product page has a Reviews and bugs section, after What's new. What's written there comes only from people who have the product, and the developer answers it in public.

Who can write

You can review a product or report a bug once you have it: you bought it, downloaded it, installed it with your token, or copied its AI prompt. The product's developer, UpFork's admins and blocked accounts can't. Anyone signed in can report a review as abuse.

Reviews

One review per product, which you can edit later (it then shows "edited"). It's tied to the version you had.

The verdict: Ship it ("Use it as it is."), With fixes ("Good, once a thing or two is sorted.") or Skip ("Not worth it as it stands.").
What's good and what isn't: up to 8 lines each, 200 characters a line, shown as green + and red − lines.
The developer's answer: one, in public, which they can edit. A developer can't hide a review; UpFork's moderators hide one only with a reason its writer reads.

In the catalog, sort by Best reviewed, or show only the products that have reviews, or those most people say Ship it to.

Bugs

Report a bug with a title, the steps to see it, and screenshots if they help (pictures up to 5 MB). Your browser and system are filled in for you. You can report up to 10 bugs a day.

Public: the bug's number (#1, #2… for each product), its title, the version, its state and the developer's answer.
Private: the steps, your browser and system, and the screenshots, seen only by you, the developer and UpFork's moderators.
States: New, Confirmed, In progress, Fixed (in a version), Won't fix, Duplicate.
Me too: if you have the product and hit the same bug, press Me too, and you're told when it's fixed as well.

Each bug has a page of its own, at the product's address plus /bugs/<number>.

When a developer publishes an update whose notes say "fixes #12" (or "fixed", "closes", "resolves"), bug #12 is marked fixed in that version a couple of minutes after the update goes out, and everyone who reported it or said Me too is told, by e-mail too.

Once five bugs have been reported on a developer's products, how they answer shows on the product page, their profile and their PDF résumé: "usually answers bugs within a day · 9 of 10 fixed".

What's new and Watch

Every product page has What's new: its releases and code versions, newest first, with the latest version beside "Updated".

If you have the product, it says which version you have: "You have v1.2 · v1.3 is out", or "You have the latest".
Watch, beside Like, follows any product. The products you have are watched for you.
When a new version goes out, everyone who has or watches the product hears about it a couple of minutes later: on the site, and by e-mail at most once a day for each product.

Notifications

The bell in the header shows what's new for you, and Notifications lists everything. Its settings choose, for each kind (orders, your plan, selling, product updates, support, reviews and bugs, news from UpFork), whether you hear on the site, by e-mail, or both. Security notices always reach you. Notifications are kept for 180 days.

Reviews

One review per product, which you can edit later (it then shows "edited"). It's tied to the version you had.

The verdict: Ship it ("Use it as it is."), With fixes ("Good, once a thing or two is sorted.") or Skip ("Not worth it as it stands.").

What's good and what isn't: up to 8 lines each, 200 characters a line, shown as green + and red − lines.

The developer's answer: one, in public, which they can edit. A developer can't hide a review; UpFork's moderators hide one only with a reason its writer reads.

In the catalog, sort by Best reviewed, or show only the products that have reviews, or those most people say Ship it to.

Bugs

Report a bug with a title, the steps to see it, and screenshots if they help (pictures up to 5 MB). Your browser and system are filled in for you. You can report up to 10 bugs a day.

Public: the bug's number (#1, #2… for each product), its title, the version, its state and the developer's answer.

Private: the steps, your browser and system, and the screenshots, seen only by you, the developer and UpFork's moderators.

States: New, Confirmed, In progress, Fixed (in a version), Won't fix, Duplicate.

Me too: if you have the product and hit the same bug, press Me too, and you're told when it's fixed as well.

Each bug has a page of its own, at the product's address plus /bugs/<number>.

Once five bugs have been reported on a developer's products, how they answer shows on the product page, their profile and their PDF résumé: "usually answers bugs within a day · 9 of 10 fixed".

What's new and Watch

Every product page has What's new: its releases and code versions, newest first, with the latest version beside "Updated".

If you have the product, it says which version you have: "You have v1.2 · v1.3 is out", or "You have the latest".

Watch, beside Like, follows any product. The products you have are watched for you.

When a new version goes out, everyone who has or watches the product hears about it a couple of minutes later: on the site, and by e-mail at most once a day for each product.

Notifications