About
Codebase intelligence you can check.
repowise indexes a repository once and serves that index to your agents, your editor, your pull requests and your team. Everything we claim about it is published with the method that produced it.
How we work
Three things you can verify.
An engineering leader evaluating tools has been told a lot of unfalsifiable things. None of the below is one.
- 01The method ships with the numberEvery published figure carries its sample size, its corpus and its caveat. Code health scores 0.74 ROC AUC at predicting which files get bug-fixed over the next six months, across 21 repositories, 9 languages, 2,826 files, with a 95% confidence interval we print next to it.Read the benchmarks
- 02You can run the whole thing yourselfrepowise 0.56.0 is open source and self-hostable. The 25 defect markers behind the health score are deterministic and run locally with no LLM and no cloud, so you can read the code that produced your score.Read the source
- 03Every release is in the openEach release is tagged on GitHub and written up in the changelog, so you can see what changed, when, and in which pull request.Read the changelog
Who builds it
The people behind repowise.
Small team, public work. The commit history is the resume.
- 01Raghav ChamadiyaCo-founder, and author of the defect-prediction validation study behind the code-health score.Read the profile
- 02Swati AhujaCo-founder. Writes about learning a codebase you did not write, and what coding agents should know before they change one.Read the profile
- 03Contributorsrepowise is developed in the open. Issues, discussions and pull requests all live on GitHub.Open the repository
Judge it the only way that counts: on your own repo.
Index a repository free in minutes. Rolling it out to a team? We will walk you through it.