Publish to the store
Paste the address of your repository. Terminal Deck reads it, shows you exactly what would be listed, and puts it in the queue.
New to this? What you can publish → — the seven kinds, how a price works, and one listing read end to end.
Sign in first
Publishing needs a GitHub sign-in — only GitHub can confirm a repository is yours. Everything else on the site takes either sign-in.
The first time you sign in, your account is made and you pick the name your work is published under. Signing in publishes nothing by itself.
Choose your publisher name
It goes in every address your work is published at, and it cannot be changed afterwards.
Publishing needs GitHub
You are signed in as . Publishing asks GitHub whether you can write to the repository you are listing, so your GitHub account has to be connected to this one. You stay signed in as you are.
Everything else about your account — your name, your picture, your listings and what a reviewer said about them — is on your account page.
What you have already sent
A person reads every first version by hand. Nothing here needs chasing — your account page shows all of it, including anything already on the shelf.
Your repository
What would be listed
For AI readers
What happens after you press Publish
The listing is created as a draft and its first version goes into a queue. A person reads it — the files, the manifest and what it would do to somebody's machine — and then approves it, refuses it with a reason you will see, or bans the account. Nothing appears in the store until that has happened.
Afterwards, updates that do not change the risky parts publish themselves. The bytes are pinned to a commit and a sha256, so what a person reviewed is exactly what anybody installs.