←back to thread

Show HN: StackHound - Stop guessing repo's tech stack, analyze it in seconds

(stackhound.vercel.app)
8 points lorenzopalaia | 2 comments | 25 Apr 25 14:47 UTC | HN request time: 1.809s | source

If you’ve ever explored GitHub repos and felt frustrated by how little you can tell about a project’s real tech stack — you’re not alone.

That’s exactly why I built StackHound https://www.producthunt.com/posts/stackhound

It goes beyond the GitHub API to scan dependency files and uncover the actual tools, frameworks, and languages a repo uses — whether it's built with React, Next.js, Tailwind, Flask, or Spring Boot.

Just drop in a GitHub username and repo to analyze it instantly. You can also use our /api/analyze endpoint to plug it into your own tools.

Try the live demo: https://stackhound.vercel.app/ Check out the code (open source!): https://github.com/lorenzopalaia/stackhound

Would love to hear your thoughts — what features would make StackHound even more useful for you?

1. stevage ◴[26 Apr 25 00:06 UTC] No.43799681[source]▶
I cannot say I have had the experience you describe. Most repos describe their stack clearly, or you can figure it out easily enough. Is it really a common problem for you?
replies(1): >>43803731 #
2. lorenzopalaia ◴[26 Apr 25 14:04 UTC] No.43803731[source]▶
Do you mean in the project readme description? I'm talking about programming languages that are returned by the github API for a specific repo.

For example in my portfolio site I had to show the technologies used in my projects but for a nextjs project the github API returned only typescript and css while I used react, tailwind, ...