All tools · browser studios · 2026-10-15
Open a tool and work with the files you already have. 0 Craft editors have verified WebAssembly builds served from this origin after deployment; ArtCraft remains a clearly labelled upstream browser app.
13 results
No matching tool. Try a product name, file format or platform.
A project earns a page when four things are true: the repository is reachable and not archived, the licence is stated in the repository, the platform list matches the release assets rather than the marketing copy, and there is a concrete job the tool does that we can describe without adjectives. Hotness on GitHub is not one of those four.
| Check | What we look for | Why it matters |
|---|---|---|
| Repository alive | Recent commits and releases; not archived | A dead upstream means broken downloads and stale instructions |
| Licence in writing | A LICENSE file with a recognised SPDX identifier | Commercial and redistribution decisions cannot rest on a README sentence |
| Real build matrix | Release assets, not a feature list | A tool advertised for Linux with no Linux asset is not a Linux tool |
| Describable job | One sentence a user could act on | Directories of vague tools help nobody choose |
When a tool is discovered automatically through the GitHub catalogue, it enters the candidate queue first. A cautious community card may be shown in the directory for research, but it stays out of the sitemap and keeps a noindex detail page until an editor verifies the repository, release, licence and real workflow. That is a deliberate brake: an index of thin, templated app pages is worth less than two pages that answer real questions.
Core profiles need a verified repository, licence, platform list and install path. GitHub Radar can surface more community discoveries, but those cards stay cautious and noindex until an editor checks the claims. Adding volume before that would produce pages that repeat each other, which is the fastest way to teach search engines to ignore a directory.
The projects listed today publish under MIT or Apache-2.0, which permits commercial use under its terms. Read each upstream LICENSE and NOTICE file for the obligations that come with redistribution.
The upstream GitHub Release for each project. Buttons on this site route through a single exit that resolves to a configured address; no installer is stored or repackaged here.
Yes, and removal is a designed outcome rather than a failure. If a repository is archived, changes licence or its download links break, the page moves to an out-of-date state, leaves the sitemap and says what happened, when, and where the upstream record still lives.
