Wyro — Backend Architecture Check

Open any GitHub repository, press one button, and see what its backend actually does. Wyro reads the repository's database schema and its HTTP routes, builds the architecture they describe, and checks it. The rule that matters most: can any endpoint reach a database table without passing through authentication first? That is the most common way a backend leaks data. Everything runs in your browser. Source is fetched from GitHub and analysed on your own machine. Nothing is uploaded, there is no account, and no Wyro server takes part in a check. It understands the common TypeScript and JavaScript backend stacks, in both module systems. Where a project is built on something it does not recognise, it says so rather than guessing. The current list is on wyro.in. WHAT IT WILL NOT DO It will not tell you a repository is fine when it could not read it. A project it cannot parse is reported as unreadable, never as clean. Where routes are found but no schema is, the rules that needed one are listed as not having run. That is not the same as passing, and the difference is the whole point of the tool. It does not guess intent either. A public read of a product catalogue and a public read of an invoice table look identical to a parser. GOOD TO KNOW Without a token, GitHub allows 60 repository reads an hour from your network. Add a personal access token on the Options page to raise that limit and to check private repositories you already have access to. The token stays on your machine and is sent only to GitHub. For a large monorepo, open the subdirectory you care about first. The check is scoped to the path in the address bar. Wyro also compiles a backend design into a real TypeScript project — https://wyro.in