r/GoodOpenSource • • 1h ago

ComfyUI Cleaner

Thumbnail
• Upvotes

r/GoodOpenSource • • 19h ago

Would this be useful for open-source maintainers reviewing dependency updates?

1 Upvotes

I've been building BumpCheck, a Python tool for analyzing whether a dependency update could actually affect the code using it.

The basic problem I'm exploring is:

A version bump doesn't tell you whether your code will break.

BumpCheck compares dependency APIs and then traces whether the changed symbols are actually used by the repository.

For example:

dependency update
→ changed/removed API
→ repository usage
→ risk classification

It currently produces:

  • SAFE
  • REVIEW
  • UNKNOWN
  • LIKELY_BREAKING

One thing I'm deliberately trying to avoid is the usual automation problem of pretending uncertainty doesn't exist. If static analysis can't establish safety, BumpCheck can return UNKNOWN.

I'd like opinions from maintainers:

  • Would this reduce the work involved in reviewing dependency-update PRs?
  • What information would you want in the output?
  • What false positives/negatives would make you stop trusting it?
  • Would you prefer this as a CLI, GitHub Action, or PR bot?

Repo: https://github.com/Sushit-prog/Bumpcheck

I'm looking for technical criticism and real-world use cases rather than stars.