Where to Find upset.dev's Open Source Projects and How to Contribute

upset.dev lists its open source work in a dedicated Open Source section, and the page states that these projects are "available on GitHub for anyone to use, contribute, or learn from." The site itself does not publish a single repository URL or a contribution guide, so the practical path is: start from the Open Source section on upset.dev, then follow each project to its GitHub source. The one project named in the page evidence is fonts.upset.dev, described as the source code for a privacy-preserving alternative to Google Fonts.

What the Open Source Section Actually Contains

The page separates its work into two buckets:

The distinction matters. A product like Favicone is something you call as an API; an open source project is something you can inspect and modify. Some items appear in both worlds — fonts.upset.dev is listed as an open source project, while the Fonts service it powers is listed as a product.

Finding the Repositories

The page evidence names fonts.upset.dev as a concrete open source project, but it does not list repository URLs for the others. To locate the rest:

1. Open the Open Source section on upset.dev.
2. Follow the link attached to each project — the page describes these as GitHub-hosted.
3. If a project name matches a product (for example, Fonts), check whether the repository is linked from the product page or from the Open Source entry.

Because the site does not publish a consolidated GitHub organization link in the evidence provided, treat the Open Source section itself as the index rather than assuming a single github.com/upset-dev destination.

How to Contribute

The page's own wording — "use, contribute, or learn from" — sets three levels of involvement:

• Use: clone or fork a repository and run it yourself.
• Learn: read the source to see how a tool like a privacy-preserving font service is built.
• Contribute: once you are in the repository, follow its own contribution instructions. The upset.dev page does not describe a contribution process, so the repository's README, issue tracker, and license are the authoritative sources for how to submit changes.

A realistic first contribution looks like this: pick a project whose domain you already understand (for example, fonts or DNS tooling), reproduce a reported issue locally, then open a pull request against the repository's default branch. If the repository has no contributing guide, opening an issue first to ask about scope is the safer move.

What You Cannot Confirm From the Page Alone

• No license terms are stated on the upset.dev page — check each repository.
• No maintainer contact, code of conduct, or review timeline is published there.
• No repository URLs are given except the project name fonts.upset.dev.

For anything beyond "the projects exist and are on GitHub," the repository itself is the source of truth.