Skip to content
openproduct
Search

How every number is computed

Every ordering and every computed figure on openproduct resolves to one sentence, and this is the list. There is no relevance score anywhere in this product: 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.

The orders you can choose

Three, and no fourth. Each is a sentence rather than a score, which is what makes it arguable — and an order nobody can argue with is an order nobody can check.

sort.most-activeOB3

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-savedDS2

Listings ordered by the number of distinct subjects who have endorsed them and not withdrawn, all time, after the integrity discount is applied.

sort.newestDS2

Listings ordered by when they were first published, most recent first.

sort.rolesOB4

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.

What appears in the catalogue

Not an ordering. This is the one rule here that decides whether a listing is in a list at all, and it deliberately does not decide where: a listing that clears it takes exactly the position its observed activity gives it, and one that has not is absent rather than last. It asks for two things a reader needs before they can decide whether to click, and there is nothing to compete on — clearing the bar twice buys nothing.

catalog.front-page-floorIN3

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.

Search

Relevance is an editorial position wearing a technical name: it decides whose work is seen. So it is a published rule rather than a library's weighting, and it takes no input about who is searching.

search.relevanceDS0

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.

Activity

Observed from the repository, never from anything a maintainer types. A number here is always accompanied on the page by when it was observed.

activity.merges.30dOB2

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.7dSN2

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.

Upvotes

One person, one upvote, and the total is the discounted one. A save is a different, private act and is counted nowhere public.

endorsements.7dEN2

Endorsements added in the trailing seven days and not since withdrawn, after the integrity discount is applied.

endorsements.totalEN2

Distinct subjects who have endorsed this listing and not withdrawn, after the integrity discount is applied. One subject counts once.

Similar products

A recommendation is an ordering, and OPC-4 does not carve out recommendations. No embeddings, no co-visitation, no behavioural signal.

similar.same-category-then-activeDS4

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.

Launches

The board's order shares no inputs with the directory's, deliberately.

launch.board-rankLC3

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.leaderboardUV2

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.

Topics

The panel this feeds is called Active rather than Trending, and the difference is the whole rule: activity is measured, and trending would be a claim about what readers are doing that this product does not observe.

topic.recent-launchesFL1

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.

Collections

A collection is already an attributable editorial act by a named curator (LC4). There is no `featured` flag over the top of that, because a second layer of selection would be an unattributable one.

collection.newestFL1

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.

Roles a listing is looking to fill

One count and one order. A role on a quiet product is as findable as a role on a busy one — nothing here is weighted by how popular the listing is or by how many people have already applied.

openings.newestFL1

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.openCT4

Contributor openings on this listing whose status is open.

People

Nobody is ordered by merit anywhere on this estate. The one people-ordering that exists lists those who ticked `open to one more project` themselves, in the order they ticked it — not by the upvotes their products earned, not by how much they have launched, and not by how many already follow them.

people.open-to-projectFL1

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.rosterCG3

Maintainers and contributors whose place on this listing both the maintainer and the person themselves have confirmed. Unconfirmed entries are not counted.

Comments

A comment's upvotes are public and one per person, and they change nothing about what anybody is shown — comments appear in the order they were written. That is why this is the one count here with no integrity discount: the discount protects orderings, and this is not one.

comment.votesDQ1

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.

A maker's own page

What a person did, in the order they did it — never a ranking of people. The upvotes tab lists a public act the vote control announces at the moment it is pressed; a save is private, is counted nowhere, and has no tab.

maker.commentsMP0

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-launchPE2

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.historyPE1

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.launchedMP0

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.upvotedMP0

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.

The numbers on a person's profile

Held to a higher bar than anything else here, because they are claims about somebody's work rather than about a product. Each is counted from acts that person took: a role they hold, a place they confirmed. One of them is deliberately absent rather than zero — nothing observes it, and inventing a number about a person is the one place a made-up figure does real harm.

contributor.contributes-toCG4

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.followersFL0

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.maintainsCG4

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.12moCG4

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.sinceCG4

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.

Counts on the page

Whatever is left: figures that are not orderings but are still computed, and therefore still owe a sentence.

alternatives.overlapPV2

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.

digest.most-endorsedLC1

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.

facet.countCT4

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.countPP1

People following this listing right now. Counted at read time and never listed — nobody can see who they are, including the maintainers.

integrity.discountEN3

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.

listing.indexableTS1

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.

product.crew-countOPR2

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-shippedOPR2

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.stageOPR2

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.languagePV0

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-commitPV0

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.licencePV0

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-issuesPV0

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.

team.size-bucketCG3

The bucket this listing's confirmed roster falls into: solo, 2–3, 4–10, 11–30, or more than 30.

threads.latestFO1

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-repliedFO1

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-repliedHB3

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.

votes.cleanPV3

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.

What we know is wrong with these orders

Not every product can be measured the same amount. A product whose repository is linked through our GitHub integration can be read fully; a product that only declares a public URL can be read partly; a product that declares neither is not read at all. Ordering by activity therefore favours the first group. We render the gap as an absence rather than as a low score — a dash, never a zero — but it is a real bias in the default order and you should know it is there.

Activity is gameable, and it is ranked on. The default order is sort.most-active, so the exposure is real rather than theoretical. Four things blunt it, and we would rather name them than imply there is more: the metric counts merged changes, not pushes; it is capped per contributor per day, so one person or one agent cannot manufacture activity alone; it is multiplied by counted upvotes, so work nobody wants does not lead on its own, and the upvotes are counted after the integrity discount; and the figure renders beside the team size, which makes an implausible ratio visible to a reader rather than only to us.

There is no anti-gaming model beyond that, and that is a choice rather than an omission. A real one needs opaque adjustments — a score nudged for reasons nobody publishes — and an unexplainable rank cannot be defended to the maintainer whose launch sank because of it. We would rather have an order that can be gamed and argued with than one that cannot be either.

Nothing here can be bought. There is no paid placement, no sponsored listing, and no way to pay for position in any of these orders.