alt.hn

4/25/2025 at 2:47:09 PM

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

https://stackhound.vercel.app/

by lorenzopalaia

4/25/2025 at 8:34:48 PM

I tried it on https://github.com/monkeytypegame/monkeytype and it just said ESLint and Prettier which doesn't describe much. It probably would work properly if it worked recursively or at least checked the first directories. I like the website and api option though.

by lukew3

4/26/2025 at 2:01:28 PM

For now the strategy is to check the manifests in the root of the project without fetching to the github API. Alternatively you can check recursively and search for manifests and other files also via API but you lose the speed of response. It is a first draft and above all an open source project and I would like someone to contribute.

Thanks for the feedback on the website. The API is intended as a core product, to help developers who integrate the github API to get programming languages from a repo.

by lorenzopalaia

4/26/2025 at 12:06:02 AM

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?

by stevage

4/26/2025 at 2:04:24 PM

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, ...

by lorenzopalaia