We read what you build and what you build it with, then answer the three questions worth answering this week — what to fix, what to adopt, what to read.
Questions
What do you actually read?
The repository description, its topics, the language breakdown, the README, and any dependency manifests we can find (package.json, requirements.txt, pyproject.toml, go.mod, Cargo.toml). Public data only — no access grant, no OAuth, nothing installed.
Do you store my code?
No. We never clone the repository. We read a handful of public files through the GitHub API and keep only the derived profile — the summary paragraph and the dependency names — so a repeat scan is instant.
Can I scan a private repo?
Not yet. Everything here runs on public data. If your work is private, run the free Stack Audit instead: paste the manifest directly and nothing is stored at all.
What if the summary is wrong?
The three panels are driven entirely by that paragraph, so if it misses the point the results will too. It is editable once you have an account — and for a company whose repo is not representative, writing the context by hand is still supported.