Badges
Last updated 2026-10-23
Open-source projects listed on OSSHunt can show a README badge naming the paid tools they are mapped against. The badge links to the project's OSSHunt page, where the fit, license, paid-feature tier and migration notes for each tool are shown with sources.
What it means
- OSSHunt lists the project as an open-source alternative to the paid tools named on the badge.
- Each named tool has a mapping with partial fit or better. Partial means core overlap with named gaps; it is not feature parity.
- It is an editorial listing from public sources at the date checked. It is not an endorsement by the paid vendors, a security review or a production recommendation.
- Paid tools are named in text only. Names belong to their owners and identify the products.
Which projects are eligible
All of these must hold. 91 of 132 listed alternatives qualify today.
- The core edition uses an OSI-approved license: paid-feature tier A, B or C. Source-available (S) and unresolved (U) entries are excluded. Tiers explained.
- The repository is not archived or disabled.
- At least one mapping to a paid tool has fit "drop-in" or "partial". Mappings marked "different approach" are not named. Fit explained.
Up to three paid tools are named, in alphabetical order. With more than three, the badge shows the count, for example "replaces 6 paid tools"; the profile page lists them all.
Adding it
Each eligible project page has a "Selected by OSSHunt" section with Markdown, HTML and reStructuredText snippets. The image is https://osshunt.com/badge/<id>.svg; add ?style=flat-square, plastic or for-the-badge to match a badge row. A Shields endpoint is at https://osshunt.com/badge/<id>.json.
Removing it
Delete the badge line from your README. Nothing else is needed. Badge requests set no cookies.
If a project stops qualifying, for example after a license change or an archived repository, its badge shows "not listed" instead of the paid tools, so a README never keeps a stale claim.
How listings are chosen and corrected
Paid tools are chosen by how many businesses are likely to use them; alternatives are researched from license files, edition comparisons, pricing pages and repository activity, and every claim keeps its source and date. Fit is judged per pair of products. The method page has the details.
If an entry about your project is wrong or out of date, or you want it removed from OSSHunt, email hello@osshunt.com with the source. We aim to correct verified errors; corrections show on the badge at the next update.