Whatever is left: figures that are not orderings but are still computed, and therefore still owe a sentence.
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.
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.
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.
People following this listing right now. Counted at read time and never listed — nobody can see who they are, including the maintainers.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The bucket this listing's confirmed roster falls into: solo, 2–3, 4–10, 11–30, or more than 30.
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 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 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.
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.