A project page belongs to whoever can prove they control the repository. Sign in, open the project page, hit "Claim this project", and pick a route — each takes about a minute.
Route oneConnect the account
Link the GitHub or Hugging Face account behind the repository and 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.
Reads your public identity only — no repository scopes.
Route twoPublish a token
The claim page shows a token tied to your account and that one project. Commit it as taxoss-verify.txt at the repository root — or paste the line anywhere in the README — and verify. We fetch it anonymously, like any visitor. Delete it afterwards; the claim stays.
No account access at all — publishing in a repo you control proves control and grants us nothing.
Neither fits?We'll verify by hand
A protected default branch, an organization that blocks OAuth apps, a handover between maintainers — email pascal@lurn.digital and we'll sort it out manually.
Manual grants are logged separately, so they stay distinguishable from self-verified claims.
Verified maintainers get the maintainer mark and can edit the project's name, tagline, website, and categories. Everyone else can star, review, and comment.