How this works.

Claiming a project

A project page belongs to whoever can prove they control the repository. There are two ways to prove it, both about a minute. Sign in, open the project page, hit "Claim this project", and pick one.

Connect the account

1. Link the GitHub or Hugging Face account behind the repository.
2. Verify. We ask the source whether your account controls the repo — GitHub admin permission, or a matching Hugging Face identity. One click, checked server-side.

For GitHub and for personal Hugging Face repos this reads your public identity only, no repository scopes.

Or publish a token — no account access at all

1. The claim page shows you a token. It is tied to your account and that one project, so nobody else's token will work and yours is worthless anywhere else.
2. Commit it to a file called taxoss-verify.txt at the root of the repository, on the default branch. Pasting the same line anywhere in the README works just as well.
3. Come back and verify. We fetch the file the way any visitor would — anonymously, over the public URL. Delete it afterwards if you like; the claim stays.

This route exists because Hugging Face has no read-only "which organizations am I in" scope: the only scope that proves membership also grants read access to an account's private repositories. Publishing a token in a repository you already control proves the same thing and grants us nothing.

If neither route fits — a protected default branch, an organization that blocks OAuth apps, a handover between maintainers — email pascal@lurn.digital and we'll verify it by hand.

Verified maintainers get the maintainer mark and can edit the project's name, tagline, website, and categories. Everyone else can star, review, and comment.

Stay in the loop

Every few weeks we send one email listing the newly featured open-source tax projects. No noise, unsubscribe any time.