Publish a widget
Upload a widget package. It's checked at once, reviewed by a person, then listed for everyone.
Sign in with GitHub
Your GitHub account is your author name, and where reviewers can reach you.
Upload the package
A zip of the package's files, at the top of the zip rather than in a folder, at most 1 MB. Or share it straight from the desktop app once it can.
Read the report
The checks run as soon as the upload lands. Fix anything that fails and upload again; anything flagged goes to the reviewer with your notes.
Before you upload
Zip the files
The package's files themselves, not the folder they're in, with your GitHub login as the manifest's author. The upload's report says what to fix.
Pick a license
Any OSI-approved license, with its LICENSE file in the package.
Ask for little
Every permission needs a reason your README gives. Secrets only go to the service that issued them.
What we check
Blocks the upload
Zip layout, allowed files and size limits
Blocks the upload
manifest.json is valid, and the id is yours and not reserved
Blocks the upload
The version is higher than the last one published
Blocks the upload
view.json is valid, and every binding, source and button is declared
Blocks the upload
An OSI-approved license, with a LICENSE file
Blocks the upload
collector.js is one ES module with no imports
Blocks the upload
No credentials embedded in the code
Goes to review
No minified or obfuscated code
Goes to review
The collector runs in the sandbox with sample data, within its limits
Goes to review
Secrets only go to hosts of the service that issued them
Goes to review
Revealing sources together with network or local access. Always reviewed by a person.
Goes to review
Access to apps on this PC or network
Goes to review
No hosts on tracking or analytics blocklists
Goes to review
The GitHub account is at least 30 days old
Goes to review
Permissions added since the previous version. Always reviewed by a person.
Goes to review
AI review: does the code do what the description and permissions say?