The browser half is ready to submit; what is left is a payment and a form.
The fee
US$5, once, per developer account. Not annual, not per-extension. Collected in the Chrome Web Store developer dashboard during signup.
Free alternatives do not reach the same people: Edge Add-ons has no registration fee but only serves Edge, and Chrome blocks installing a self-hosted .crx on Windows and macOS. Firefox AMO is free but this extension's core is chrome.proxy with an inline PAC, and Firefox's browser.proxy is a different API.
It is not needed to use ssh-browser. Loading extension/dist unpacked works and is what is happening today. The fee buys distribution — auto-updates, no developer-mode nag, and a link to hand somebody. That matters once the daemon has users, so this is deferred rather than dropped.
Suggested: publish Unlisted first
Installable by link, not in search results. Auto-updates and the nag gone, without betting on the quality of a public listing. Can be switched to Public later.
Already done
extension/STORE.md — single purpose, short and detailed descriptions, per-permission justifications, categoryPRIVACY.md — usable as the policy URL directly: https://github.com/QAtlasHub/ssh-browser/blob/main/PRIVACY.md- Screenshots at 1280×800 from the live product:
npm --prefix e2e run shots
- The zip is attached to every GitHub release automatically, byte-identical between builds
- Permissions are down to
proxy, storage, http://127.0.0.1/* — no scripting, no optional host permissions, no permission prompt anywhere in the product
- A first run with no daemon explains what ssh-browser is and what to run, so a reviewer installing it with no daemon does not meet a dead end
Steps when the time comes
- Register at https://chrome.google.com/webstore/devconsole and pay the $5
- Upload
ssh-browser-<version>.zip from the latest GitHub release
- Paste the text from
extension/STORE.md, attach the screenshots, set the privacy policy URL
- Choose Unlisted
- Submit, and expect a review
Keep in step
extension/STORE.md and PRIVACY.md justify a permission set. If the manifest's permissions change, both have to change with it — a listing that describes permissions the package does not ask for, or omits ones it does, is a policy problem rather than a documentation one.
The browser half is ready to submit; what is left is a payment and a form.
The fee
US$5, once, per developer account. Not annual, not per-extension. Collected in the Chrome Web Store developer dashboard during signup.
Free alternatives do not reach the same people: Edge Add-ons has no registration fee but only serves Edge, and Chrome blocks installing a self-hosted
.crxon Windows and macOS. Firefox AMO is free but this extension's core ischrome.proxywith an inline PAC, and Firefox'sbrowser.proxyis a different API.It is not needed to use ssh-browser. Loading
extension/distunpacked works and is what is happening today. The fee buys distribution — auto-updates, no developer-mode nag, and a link to hand somebody. That matters once the daemon has users, so this is deferred rather than dropped.Suggested: publish Unlisted first
Installable by link, not in search results. Auto-updates and the nag gone, without betting on the quality of a public listing. Can be switched to Public later.
Already done
extension/STORE.md— single purpose, short and detailed descriptions, per-permission justifications, categoryPRIVACY.md— usable as the policy URL directly:https://github.com/QAtlasHub/ssh-browser/blob/main/PRIVACY.mdnpm --prefix e2e run shotsproxy,storage,http://127.0.0.1/*— noscripting, no optional host permissions, no permission prompt anywhere in the productSteps when the time comes
ssh-browser-<version>.zipfrom the latest GitHub releaseextension/STORE.md, attach the screenshots, set the privacy policy URLKeep in step
extension/STORE.mdandPRIVACY.mdjustify a permission set. If the manifest's permissions change, both have to change with it — a listing that describes permissions the package does not ask for, or omits ones it does, is a policy problem rather than a documentation one.