Every single team that I worked with always used tens (if not hundreds) of dependencies. There are usually two popular options: either you ignore the dependencies problem until it's too late and hard to migrate everything to newer versions (say hi to vulnerability issues), or you're constantly trying to find the balance between working on a product and doing its maintenance.

I decided to create DepsHub to solve these particular problems:

- Update noise. There is no need to update EVERY single library all the time. Your project should be relatively up to date with all the major packages updated and no security issues.

- Automatic major updates. Breaking changes occur all the time, and LLM are quite good at this point to take the changelog changes and apply them to the codebase automatically.

- Observability. I want to know what's the current status of all of my repositories, how outdated they are, and what I need to do to make it better. This is quite a new niche that not a lot of products are focusing on.

DepsHub is processing thousands of changelogs and release notes, converting your codebase to embeddings and applies LLMs to fix any breaking changes that occur. It also uses some additional analysis to understand if the library is actually needed to be updated (some libs are having new versions every week!).

Let me know if you have any questions or suggestions. Feedback is more than welcome!

Website: https://depshub.com/

ProductHunt launch: https://www.producthunt.com/posts/depshub-2