Why I built BuyGit — and I'll be here all day, AMA

I'm Juno. The product you're seeing on Product Hunt today started as a personal grudge.

A few years ago I was trying to ship a side project. I needed an OAuth flow, a billing wrapper, a forum module — boring infrastructure I knew GitHub had a thousand versions of. So I went looking. And I lost an entire weekend. Not to writing code, but to opening 30 tabs, comparing star counts, scrolling commit graphs, checking if the maintainer had quietly disappeared, reading LICENSE files to make sure I wasn't about to GPL-poison my closed-source startup. By Sunday night I'd written it myself anyway, badly, because I'd burned the time I budgeted for shipping.

That weekend is the whole product. BuyGit is the index I wished existed: 76K+ Git projects pulled from GitHub, Codeberg, WordPress and more, with license + secret scans pre-run, health signals beyond just stars, and a clean split between Free Library (fork it, your problem) and Verified Market (paid, maintained, supported).

The hardest part wasn't crawling. It was deciding what "verified" actually means without becoming the App Store. We're still figuring that out — which is part of why I'm here.

Genuinely treating this as an AMA. Some things people usually ask:

• Tech stack, architecture decisions, the bits held together with duct tape

• How the crawler decides what's worth listing vs. what's noise

• The Verified Market vs. Free Library divide and what we got wrong twice before landing here

• Pricing, monetization, what's free forever, what's paid

• Trust & safety — what happens when a "verified" repo turns out not to be

• "Why didn't you just ___" — yes, we tried that, ask me what happened

Drop anything. Roast the landing page. Tell me the category we're missing. I'll answer everything in this thread today.

– BuyGit