Before npm install-ing something new, a quick look at its actual GitHub repo — how big it is, how much code it really contains, how it's organized — is worth ninety seconds. RepoKit makes those ninety seconds genuinely useful instead of a slow scroll through a README.
A polished README says a lot about how a project presents itself, but very little about what you're actually pulling into your dependency tree. Is this a focused, 400-line utility, or an 60,000-line framework with a narrow README that undersells its actual scope? Is the source code organized in a way that suggests active, careful maintenance, or does it look abandoned and untouched?
RepoKit gives you a fast, structural answer to those questions directly on the repository page — size and line-count estimates across every folder, letting you see at a glance whether the "core" folder is a lean 800 lines or a sprawling 12,000, before you've committed fifteen minutes to reading through it manually.
This is a structural first pass, not a security audit — pair it with your normal vulnerability-scanning tools (npm audit, Snyk, or your org's standard process) for anything you're actually about to depend on in production.
RepoKit shows you the real scope of a package's repo in seconds, right on the GitHub page.
Add RepoKit to Chrome — it's free
Repo