What this is

How it works

Every page is derived from one configured authority: the validated repository seed by default, or the published PostgreSQL catalogue after an explicit cutover. A category page cannot list a product that does not claim that category, because there is no separate category record that could drift out of step with the products underneath it.

Projects and proprietary products are the same catalogue record with different structural facts attached. A Project can be OSI-approved open source, source-available, custom-licensed, or license-unknown; public source code alone never upgrades its label. A star count cannot appear on a proprietary product and a price cannot appear on a Project, because the shape of the data does not permit it.

Star counts, commit dates, and versions are a snapshot taken on 31 August 2026. They are presented as figures on a page, not as live readings, and nothing here claims a freshness it does not have.

What it does not do

Paid placements and affiliate deals, when enabled, are labelled and kept outside organic ranking. Optional accounts store only the private state described in the privacy policy. Safe outbound and commercial events use bounded pseudonyms rather than raw identity, IP addresses, cookies, or browser fingerprints. Newsletter addresses are encrypted and require confirmation; suppression is retained only to honour opt-out.

Descriptions are written for this project rather than copied from elsewhere. Repository facts come from public data, and pricing was recorded from public pages on 31 August 2026.

Product icons are requested from Google’s favicon service rather than served from this repository, which means that service can see which product pages get viewed. The request carries a website address, and a product whose icon cannot be fetched simply shows its initials instead. Configured account, newsletter-delivery, and anti-abuse providers receive only the data needed for their stated purpose; disabled features make no provider call.

Reading the listings

A product is anything you could adopt, a Project or proprietary, and every Project states its reviewed license policy next to its name. A category says what a product is for, while a tag says what it is made of or how it is run. That distinction is kept consistently, in the interface and in the code.

Where a category has no open source answer at all, the page says so plainly rather than leaving an empty section. Music streaming is the clearest case: the constraint there is catalogue licensing, not software.

Start from a product you already use, or from what you are trying to do.