Repeated filenames hide in plain sight across large repositories — GitHub's folder-by-folder view gives you no way to notice them without checking every directory by hand. Here's a faster way.
To manually find every place a filename like config.ts appears in a large repository, you'd need to either remember every folder you've opened and cross-reference by hand, or use GitHub's search with a filename: qualifier and page through results — workable, but slow, and easy to miss instances in folders you haven't thought to check.
If you already suspect a specific filename might be duplicated, searching for it with RepoKit's Ctrl/Cmd+Shift+K search shows every matching path at once — a quicker route than waiting to spot a badge if you know what you're looking for.
Not every duplicate is a problem — monorepos legitimately reuse filenames like index.ts or README.md per package, and that's expected structure, not an issue. The value of surfacing them is giving you the choice: confirm the repetition is intentional, or catch the genuine accidents — a leftover copy, a build artifact committed alongside its source — before they cause confusion for the next person who opens the repo.
Repopackage.json and README.md is expected and informative), not just a tool for finding mistakes.index.ts) and reviewing every flagged instance is the fastest path today.RepoKit flags every repeated filename automatically as you browse.
Add RepoKit to Chrome — it's free