Baur – incremental build tool for monorepos

I built SimRepo, a browser extension that adds a “Similar Repositories” panel directly into GitHub repo pages (for repos with 150+ stars). It's useful for discovering related projects while browsing. It's based on a vectorized model trained on GitHub star data. Repo: https://github.com/Mubelotix/SimRepo Chrome/Firefox support, no tracking, fully open source. Would love feedback on the recommendation quality or UX!

A multi-language monorepo tool

Hey HN - today I’m launching GitHired. A hiring platform that ranks developers based on what they actually build — not what they claim on a PDF. It’s called GitHired, and here’s the core idea: GitHub > Resumes Instead of trusting “proficient in React” bullet points, we analyze a candidate’s actual GitHub: their real tech stack their most complex projects how active they are what kinds of contributions they make which skills match your job description and yes, we detect fake “green square farming.” Why we built this Because engineering hiring is broken. Resumes are inflated. Activity charts…

Bake, A build system for building, testing and running C & C++ projects - SanderMertens/bake

Hi there, I've been working sporadically over the last six months on a go monorepo tool (0 config it just use go workspace and go convention). It’s basically like TurboRepo but without the task runner. The tool builds a dependency graph between packages, allowing you to do things similar to what you can do in TurboRepo, like "only test the packages and the packages that depend on them, compared to the main branch," or "only install dependencies for Package A and its dependencies," etc. I use native go tool to get dependencies and create dependency graph between the package.Nothing crazy but…

Hey HN! We just launched open sign up on Buildstash. It's a platform for managing and sharing software binaries. I'd worked across game dev, mobile apps, and agencies - and found every team had no real system for managing their built binaries. Often just dumped in a shared folder (if someone remembered!). No system for versioning, keeping track of who'd signed off what when, or what exact build had gone to a client, etc. Existing tools out there for managing build artifacts are really focused on package repository management. But miss all the other types of software not being deployed that…