Submit a firmware

Paste a GitHub repository. EspAtlas Jr scores it with the catalog's fixed rules and opens a cited pull request — no login, no account.

The submit box is not switched on in this deployment. Open a submission issue on GitHub instead — it goes through the same gate.

What happens next

  1. Your submission becomes a public GitHub issue labelled submission, opened by the EspAtlas Jr bot. That is the only thing this box does.
  2. Jr checks submissions on its hourly schedule and applies the catalog's fixed rules: a real public repository with at least 25 stars, 25 forks, or an independent project homepage. The homepage must be an external site rather than GitHub or a GitHub Pages mirror. The repository must also identify at least one catalogued board through the submission or its own release assets and platformio.ini, and cannot be a fork of firmware already listed. These checks are deterministic.
  3. Jr comments the verdict on the issue. If it passes, Jr opens a pull request with a cited firmware record and its first recipe; automated checks must pass, and a human maintainer reviews it before it publishes. Then it maps every board the repo's build files name.

A separate launcher-catalog intake can also qualify firmware with at least 2,000 catalog-reported downloads, with recorded provenance and review. This GitHub submission form does not accept download-count claims as a qualifying signal.

Prefer GitHub? Open the submission issue yourself — same gate, same bot. Nothing typed here is stored by this site. How we work →