The catalog, and how to read it
Everything on openproduct is available as JSON, and every field says where it came from. That second part is the point: a catalog that hands out numbers without saying whether a person wrote them, something measured them, or we computed them is a catalog of assertions.
The API
Anonymous. No credential is accepted on any route below — the response is identical for every caller, which is what makes it cacheable and what makes it safe to hand to anyone. Cached for 60 seconds.
| GET /v1/products | Every published listing. |
| GET /v1/products/{slug} | One product. Unknown, unpublished and unreachable all answer 404 — deliberately indistinguishable. |
| GET /v1/facets | The vocabulary the catalog is filterable by. |
| GET /v1/openapi.json | The schema, version 1.5.0. |
curl https://openproduct-gateway-prod.openproduct.workers.dev/v1/products
For an agent
The same catalog, over the Model Context Protocol. Anonymous and stateless, like the routes above — there is nothing here a request to /v1/products does not answer, and no credential to obtain. The tools return the catalog card untouched, provenance and all, so anything an agent reads it can also verify by hand.
https://openproduct-gateway-prod.openproduct.workers.dev/mcp
- list_products
Every published listing in the openproduct catalog, narrowed by the published facet vocabulary. Each field carries its provenance: whether a maintainer authored it, something observed it, or it was computed. Returns the catalog's own order — this tool does not rank.
- get_product
One listing by its slug, with its components, open roles and observed metrics. Unknown, unpublished and unreachable all answer the same way, deliberately.
- list_facets
The published vocabulary the catalog is filterable by: every group, every value, and what each group counts. Call this before narrowing a query — an unknown value is refused rather than silently matching nothing.
What every field tells you
A metric is absent — never zero — when a listing’s tier cannot see it, or when what we last read has gone stale past its window. 0 merges this week says a project is dead; a project nobody measured has said nothing.
- authored
A person wrote it — a maintainer or a contributor — and it is visibly in their voice. The pitch, the tagline, an opening's description, a display name.
- observed
Something measured it, at a stated time. Comes with observedAt, always. The licence, the components, work merged in the last week.
- derived
We computed it, from a formula published below. Comes with the formula's id, so you can look up exactly what it means.
How every number is computed
Every ordering and every computed figure resolves to one sentence, and this is the list. There is no relevance score anywhere in openproduct: the default order multiplies two published counts, merged changes and counted upvotes, and nothing else. There is no engagement signal — no clicks, no dwell time, no trending. A directory that decides who gets seen should be able to say exactly how.
Every formula, one sentence each (48)
- activity.merges.30d
- Changes merged into the default branch of the linked repository in the trailing thirty days, counted once per merge and capped per contributor per day (five), never counting automation accounts.
- activity.merges.7d
- Changes merged into the default branch of the linked repository in the trailing seven days, counted once per merge and capped per contributor per day (five), never counting automation accounts.
- alternatives.overlap
- Up to four listings that share something with this one, ordered by how much they share and by nothing else. Each shared thing counts once — the same topic, the same licence, running the same way — and each stack entry both carry counts once more; the panel names beside every listing exactly what it shares. A listing sharing nothing at all is absent rather than shown as a fourth suggestion. Ties are broken alphabetically so the panel is the same for every reader and the same tomorrow. Nothing about who is reading, what they read before, what other readers opened, or how active a listing is enters this order.
- catalog.front-page-floor
- A listing appears in the catalogue on the front page once it has a one-line description and a topic. THIS IS NOT A RANKING RULE AND IT IS NOT A BOOST: a listing that clears the bar holds exactly the position its observed activity gives it, and a listing that has not cleared it is not ordered lower — it is not in that list yet. Clearing the bar twice buys nothing, so there is nothing here to compete on. Nothing else a maintainer fills in affects where anything is ordered; the studio's own checklist is advice to them and reaches no public surface. Listings that launched this week are shown under their day by the launch board's own rule and are not filtered by this one.
- collection.newest
- The most recently published collection, and nothing else about it. There is no editorial `featured` flag anywhere on this estate: a collection is already an attributable editorial act by a named curator, and a second layer of selection over the top would be an unattributable one.
- comment.votes
- Distinct people who upvoted this comment and have not withdrawn. One person counts once, an author cannot upvote their own comment, and the number is the same for every reader. IT ORDERS NOTHING: comments appear in the order they were written, and no ranking anywhere on this site takes this figure as an input. That is also why it carries no integrity discount, unlike a listing's upvotes — the discount exists to protect an ordering that decides what other people are shown, and a brigaded comment count is a wrong number beside one comment rather than a wrong page. If comments are ever ordered by it, the discount comes with that change and not before.
- contributor.contributes-to
- Published listings this person confirmed a place on and does not run — counted ever, so a listing they have since left still counts, because the work happened. Anything already counted under maintains is subtracted rather than counted twice. Invitations nobody answered are not counted, and neither is anything unpublished.
- contributor.followers
- How many distinct accounts follow this person and have not unfollowed. A count and never a list: nothing on this estate answers who they are, including to the person followed, because a public follower list turns a private subscription into a graph anyone can crawl. Counted on the request path rather than kept in a column, so it cannot drift. Honest at zero.
- contributor.maintains
- Published listings this person runs — they hold an owner or maintainer role on it, and it is public. This is the same standing that makes the profile exist at all, so the number is never zero on a page you can read. Drafts are not counted, and neither is a listing that merely names them. THIS IS NOT THE NUMBER OF LAUNCHES: publishing and launching are separate acts, so this number and `maker.launched` count different things and often differ.
- contributor.reviews.12mo
- Reviews this person left on listings whose repositories are linked, in the trailing twelve months. Absent — not zero — where the repository's reviews cannot be observed.
- contributor.since
- When this person's public profile began, to the month. Not when their account was created, and not when they first appeared on somebody else's listing.
- digest.most-endorsed
- Listings ordered by the endorsements they received DURING that week — Monday to Sunday, in UTC — after the integrity discount, with the earliest launch of the week breaking a tie. Counted over the week itself rather than over a trailing window, so a digest from a year ago still answers about the days it names. A listing with no endorsements that week does not appear; absence here means nobody endorsed it in those seven days, not that it was judged.
- endorsements.7d
- Endorsements added in the trailing seven days and not since withdrawn, after the integrity discount is applied.
- endorsements.total
- Distinct subjects who have endorsed this listing and not withdrawn, after the integrity discount is applied. One subject counts once.
- facet.count
- Public listings carrying this facet value at the last recompute. Recomputed on write and at most once every sixty seconds, which is also how stale the page itself may be.
- followers.count
- People following this listing right now. Counted at read time and never listed — nobody can see who they are, including the maintainers.
- integrity.discount
- Endorsements not counted toward a listing's public total. An endorsement is discounted when a group of accounts endorsed substantially the same set of listings within a short window, or when one account endorsed many listings faster than a person reads them. Newness alone is never a reason. Nothing is deleted, the person is never told, and a later review can restore it — we publish how many were discounted and why, in aggregate, never which listings and never who.
- launch.board-rank
- Launches from one UTC day, ordered by the endorsements that listing received during that day, after the integrity discount. Only endorsements from accounts that already existed when the launch went live are counted toward a position — a brand-new account's endorsement still counts on the listing's own public total, it just does not move a rank, which is how a bought audience is answered without anybody being detected or accused. Ties are broken by the earlier launch time, then by slug so a settled day never reorders. A closed day is final. This is not the directory's order and shares none of its inputs.
- launch.leaderboard
- Launches from one range — the trailing seven days, or the calendar month so far — ordered by the upvotes each one received on the day it launched, after the integrity discount. It pools the numbers the daily board already published, without counting anything again, so a launch's figure is identical here and on its own day's board. A launch that won a quiet day therefore sits below one that came third on a busy day, which is what a range asks and a day cannot answer. A launch the daily sweep has not counted yet is absent rather than listed at zero. Ties are broken by the earlier launch time, then by slug. There is no all-time range: an ordering that never resets ranks how long a listing has existed.
- listing.indexable
- Whether search engines are asked to index this listing. A maker's first listing is not indexed until one of theirs has been reviewed by a person; every listing after that is indexed on publication. The decision is made when the listing is published and is not revisited, so a maker's later standing never changes what an already-published page was allowed to be. The page itself is live and readable either way.
- maker.comments
- Listings this person has commented on, ordered by their most recent comment on each. The count beside a listing is how many of THEIR comments are on it, not how long the discussion is. The words themselves are not reproduced here: they are public where they were written, in the thread that gives them their meaning, and a per-person index of everything somebody has said is a different artefact from the same sentences in their own conversations. A removed comment is absent, and a listing that is no longer public is absent with it.
- maker.first-launch
- The day the earliest live launch of a listing this person maintains went live, in UTC. A date and not a rank: it says when they first launched, not how it went. Absent until a listing they maintain has launched; a listing that is no longer public takes its launches with it.
- maker.history
- Every public act this person has taken, in the order it happened, newest first: a listing they maintain going live, a comment they wrote, an upvote they gave, a role they confirmed. Each row is their own record and nothing is scored, ranked or totalled — the counters in the header are computed by their own formulas, and this is the ledger beneath them. Paged by moment: the next page is everything before the last row shown. A removed comment, a withdrawn upvote and a listing that is no longer public are absent.
- maker.launched
- Launches of listings this person maintains, most recent day first, and within a day in the order that day's board put them in. It reads the rank the daily sweep already stored rather than computing one here, so a launch's position on a maker's page and on its own day's board cannot disagree. A launch whose day is still open carries no rank yet and says so. A listing that is no longer public takes its launches off this page with it. THIS IS NOT THE NUMBER OF LISTINGS THEY RUN: publishing a listing and launching it are separate acts, so somebody can maintain two products and have launched neither, and somebody can have launched something they have since handed over. `contributor.maintains` counts the listings.
- maker.upvoted
- Listings this person upvoted, most recently upvoted first. An upvote is public and has the voter's name on it — the control says exactly that where it is pressed — and this is that same fact, listed. A withdrawn upvote is absent rather than struck through: withdrawal is the act of unsaying something in public, and a record that survived it would make it unsayable. A save is a different, private act and appears nowhere. The integrity discount changes what a listing's total counts, never whether the person who voted can see their own vote here.
- openings.newest
- Open roles from published listings, most recently opened first. Nothing about the listing's standing, how many people have already asked to help, or who is reading enters this order — a role on a quiet product is as findable as a role on a busy one, which is most of what a directory of small open products is for.
- openings.open
- Contributor openings on this listing whose status is open.
- people.open-to-project
- People who have themselves ticked `open to one more project` on their public profile, most recently published first. This is NOT a recommendation and orders nobody by merit: not by the upvotes their products earned, not by how much they have launched, and not by how many people already follow them, which would make the already-followed more followed. It is a list of people who put their hand up, in the order they put it up.
- people.roster
- Maintainers and contributors whose place on this listing both the maintainer and the person themselves have confirmed. Unconfirmed entries are not counted.
- product.crew-count
- How many people a product's page lists as its crew: the maintainers its crew published, counted. A count and never a list here; the names are on the product's page. It orders nothing.
- product.milestones-shipped
- How many of a product's milestones its crew has marked shipped, and how many it has. A milestone counts as shipped from the moment it was marked and stops counting if the mark is taken back.
- product.stage
- Retired at SC1. Until then: whether a product was an idea or was shipping — an idea until its crew marked its first milestone shipped, and shipping for as long as at least one milestone was. Since SC1 a product's stage (idea, building, stage or production) is set by its crew by hand, one step at a time, and is published as authored rather than derived; this sentence stays at its address for every link that named it. It ordered nothing.
- repo.language
- The language GitHub reports as the repository's primary one, read at the last check. It is GitHub's own determination by bytes of code, not a maintainer's answer and not this product's.
- repo.last-commit
- When the linked repository was last pushed to, as GitHub reported it at the last check. A push, not a merge and not a release — it moves when anybody pushes to any branch.
- repo.licence
- The SPDX identifier GitHub reports for the linked public repository, read at the last check. A repository declaring no licence, or declaring one GitHub cannot identify, has none here rather than a guess.
- repo.open-issues
- GitHub's own count of open issues on the linked repository at the last check, which INCLUDES open pull requests. Recorded as answered rather than adjusted: separating them would mean a second read per listing, and a number this product computed rather than one it observed.
- search.relevance
- Results ordered by where the search words were found: the exact name first, then a name that starts with them, then a name that contains them, then a stack or category value, then the tagline. Ties are broken by merged changes in the trailing seven days, then alphabetically. Nothing about who is searching, and no popularity signal, enters this order.
- similar.same-category-then-active
- SUPERSEDED BY `alternatives.overlap` (PV2) AND NO LONGER COMPUTED. It ordered up to four listings sharing this listing's category by merged changes in the trailing seven days. The sentence stays published because this address was linked from the panel it explained, and a rule that disappears leaves a reader who followed that link with no way to find out what they had been shown. What replaced it states, beside every listing, what that listing shares — and orders by that rather than by activity, so a panel no longer reshuffles because somebody else pushed a commit.
- sort.most-active
- Merged changes times counted upvotes over the trailing seven days, each plus one, highest first, so a build needs both work and interest to lead. Upvotes are counted after the integrity discount, and a build whose upvotes have not been counted yet is ranked on its changes alone. Builds whose changes are not observed are ordered last, never as zero, and among themselves by when they were published, most recent first. Ties go to more merged changes, then to the more recently published build; two builds equal on all of those are ordered by their address, so a page boundary falls in one place. Merged changes are counted, not pushes, and are capped per contributor per day.
- sort.most-saved
- Listings ordered by the number of distinct subjects who have endorsed them and not withdrawn, all time, after the integrity discount is applied.
- sort.newest
- Listings ordered by when they were first published, most recent first.
- sort.roles
- Builds with at least one open role, in the Most active order. How many roles a build has open does not move it, and a build with none is not on this list.
- team.size-bucket
- The bucket this listing's confirmed roster falls into: solo, 2–3, 4–10, 11–30, or more than 30.
- threads.latest
- Threads on public listings, newest thread first — the moment the thread was started, and nothing else. Every category counts the same; a reply does not move a thread here. Nothing about who is reading enters it.
- threads.most-replied
- Threads on public listings by how many visible replies each has, most first, ties broken by the latest reply. The count is the thread's own visible comments — the same number its row shows and the launch row shows — so a removed comment neither counts nor ranks. This is not hot: a thread with many old replies stays above one with a few new ones. Nothing about who is reading enters it.
- threads.recently-replied
- Threads on public listings, most recently replied first — the moment of the latest visible comment, and nothing else. The count beside each is the thread's visible comments, by the same rule the launch row's count uses, so the two are one number. A comment a moderator removed neither counts nor moves a thread up. This is not popularity: a thread with one new reply outranks one with fifty older ones. Nothing about who is reading enters it.
- topic.recent-launches
- Topics ordered by how many launches they held in the last thirty days, most first, ties broken alphabetically. A topic with none in that window is not listed. Nothing about who is reading enters this order — not what they opened, not how long they stayed, and not how many people follow the topic, which would make the already-followed more followed. The panel this feeds is named for activity because activity is what it measures.
- votes.clean
- A mark shown on a listing whose upvotes were checked by the integrity model and almost none discounted: at least 10 counted upvotes, and no more than 5% of everything cast set aside. IT ORDERS NOTHING — the directory and the launch board read the discounted TOTAL, which already reflects the same check, and ordering by this as well would count one defence twice. NO NUMBER IS PUBLISHED PER LISTING, here or anywhere: the ratio is computed where the rows are and only the mark leaves. And an ABSENT mark is not a finding — the great majority of listings have too few upvotes to check at all, so no mark covers both the listing nobody has voted on enough and the listing that did not clear the bar, and nothing distinguishes them.
Read them in full, with what we know is wrong with them →
What runs automatically, what it may do, and how often it is wrong →
Every act of moderation, counted — including the ones we reversed →
The API's changelog, and what it promises not to change →
What we do when something is stale, and what you would see →
What the catalog is filterable by
- Category · assigned
What kind of product this is. One per listing, picked by its maintainers. Deliberately coarse: a taxonomy fine enough to be precise is one nobody navigates.
- Stack · assigned
What it is built with, canonicalised so a count means one thing. A maintainer may write anything; entries this vocabulary does not recognise stay on the page in their own words and are not counted.
- Licence · assigned
The licence observed on the linked repository at publish — not a maintainer's claim. `No licence detected` is a real answer and is shown as one: what a product is licensed under is information a reader wants, and this directory does not adjudicate which licences are acceptable (see 'What qualifies' on this page).
- Openings · derived
What kind of commitment this listing's open contributor roles ask for, taken from the openings themselves. A contributor choosing where to spend an evening is asking this question, not 'how many roles are open'.
- Activity · derived
How recently work landed, from the linked repository. `Not observed` is its own bucket and is not a synonym for quiet: a listing whose repository we cannot read has not told us it is inactive.
- Team size · derived
How many people are confirmed on this listing — maintainers and contributors who both were named and agreed to appear. Unconfirmed entries are not counted.
- Hosting · assigned
Where the product runs for the person using it. The question a reader is actually asking is 'can I run this myself, and do I have to?'
- Pricing · assigned
What using the product costs, as its maintainers describe it. Nothing here is a price this directory charges or checks.
The front-page floor
A published listing appears in the front page's catalogue once it has a one-line description and a topic. Until then it is not ranked lower — it is not listed there yet. It is still in the directory, still at its own address, and still in the API. The front page says how many listings the floor is holding back, and a maintainer sees which fields on their listing's checklist in the studio.
Publishing and launching are two things
Publishing makes your page exist. Launching puts it on the board on a day you choose. You can publish quietly, get it right, and announce it whenever you are ready.
A listing launches once per version. A listing can be launched again 180 days after its last launch, with a different version. The board is for new things. That is two rules at once, on purpose: the version is yours to name and stops the accidental repeat, and the cooldown is ours and stops the deliberate one. A label anybody can type is not a limit.
A scheduled launch is invisible until its moment — not on the board, not in the digest, not on your own page. If the listing is not published when the moment comes, the launch is missed rather than fired: we will not announce a page nobody can open. Nothing is announced, the version stays free, and you can schedule it again.
The weekly digest
What happened on openproduct in one week: everything launched, and the listings people endorsed most while it was happening. One page per week, and every week stays where it is.
There is no email signup, and no address stored anywhere on this side. The digest is a page at /digest with an RSS and a JSON feed, and every week keeps its address forever.
Weeks are ISO weeks — Monday to Sunday, in UTC — which means a week’s year is not always its dates’ year: 30 December 2025 is in 2026-w01. That looks like a mistake and is the standard behaving correctly, so every digest prints the days it covers. A week gets its page once it has ENDED: “what happened” and “what has happened so far” are different claims, and only one of them is worth archiving.
How fast you can do things
Every write has a limit, and the limits are here because a product that says no and will not say why is a product you cannot plan around. Each has two windows: a short one that catches a script, and a long one that catches the patient version of the same script. Both have to pass.
| Action | Burst | Sustained |
|---|---|---|
| endorse | 12 / minute | 300 / day |
| follow | 30 / minute | 500 / day |
| save | 40 / minute | 2000 / day |
| handle-claim | 3 / minute | 10 / day |
| profile-write | 20 / minute | 500 / day |
| listing-write | 20 / minute | 500 / day |
| listing-publish | 5 / minute | 40 / day |
| post | 10 / minute | 300 / day |
| thread-create | 3 / minute | 40 / day |
| collection-create | 2 / minute | 20 / day |
| report | 10 / minute | 100 / day |
| appeal | 3 / minute | 20 / day |
Going over gets you a 429 with a sentence saying what happened and a Retry-After saying how long — and nothing you did is lost.
One limit is not published, and here is why. Alongside the per-person limits above, some actions also have a bound per listing — a ceiling on how fast one product can be endorsed by everybody at once. Those exist to slow a coordinated arrival down enough to be visible. Publishing the exact number would tell anyone planning one precisely how many accounts to bring, so the bound is stated and the figure is not. It is set well above what a product having a very good day reaches.
What qualifies for a listing
A product qualifies if its repository can be read. That is the whole bar, and it is a bar about checkability rather than about licensing: if nobody can read the code, nothing on the page is verifiable.
The licence is shown, not judged. We display what was observed on the repository — including no licence detected, which is information a reader wants. openproduct does not adjudicate which licences count as open. Doing so would put this directory in the business of settling licence disputes within a month, and the facet plus the visible licence lets every reader apply their own bar.
A ranking bias we should state. A product whose repository is linked through our GitHub integration can be measured more fully than one that only declares a public URL, and a product that declares neither is not measured at all. Ordering by activity therefore favours the first group. We show the gap as absence rather than as a low score, but it is a real bias and you should know it is there.
Nothing on openproduct can be bought. There is no paid placement, no sponsored listing and no way to pay for position — in the default order or anywhere else.