u/MainWild1290

▲ 8 r/projects+3 crossposts

I kept running into libraries that slowly became inactive:

  • no commits
  • stale issues
  • unclear maintainer activity

Usually you only notice after something breaks.

So I built a small OSS tool called DepWatch CLI.

It scans a GitHub repo, analyzes dependency health signals, and highlights potentially risky or abandoned dependencies.

Current signals include:

  • commit activity
  • release activity
  • contributor count
  • issue activity
  • maintenance heuristics

Example output:

depwatch scan <repo_url>

It gives:

  • health status
  • risk score
  • confidence level
  • actionable hints

Still early-stage and actively improving.

Would love:

  • feedback
  • false-positive reports
  • contributor ideas
  • thoughts on scoring heuristics

GitHub:
https://github.com/pranavkp71/DepWatch

Landing page:
https://pranavkp71.github.io/DepWatch/

If you find the project useful, consider starring the repo and contributing, feedback, ideas, and PRs are all welcome.

u/MainWild1290 — 1 day ago

I kept running into libraries that slowly became inactive:

  • no commits
  • stale issues
  • unclear maintainer activity

Usually you only notice after something breaks.

So I built a small OSS tool called DepWatch CLI.

It scans a GitHub repo, analyzes dependency health signals, and highlights potentially risky or abandoned dependencies.

Current signals include:

  • commit activity
  • release activity
  • contributor count
  • issue activity
  • maintenance heuristics

Example output:

depwatch scan <repo_url>

It gives:

  • health status
  • risk score
  • confidence level
  • actionable hints

Still early-stage and actively improving.

Would love:

  • feedback
  • false-positive reports
  • contributor ideas
  • thoughts on scoring heuristics

GitHub:
https://github.com/pranavkp71/DepWatch

Landing page:
https://pranavkp71.github.io/DepWatch/

If you find the project useful, consider starring the repo and contributing, feedback, ideas, and PRs are all welcome.

u/MainWild1290 — 16 days ago
▲ 165 r/ShittySysadmin+1 crossposts

Yesterday we had a migration that added an index to a large table without thinking much about it.
Turns out it locked the table and took the whole app down for 20 minutes.

It wasn’t caught in code review, and our CI didn’t flag anything.

Now we’re trying to figure out how to prevent this kind of thing from happening again.

For teams that run migrations regularly:

  • Do you have any safeguards in place?
  • Do you rely on code review only?
  • Have you had similar incidents?

Curious what’s actually working in practice.

reddit.com
u/MainWild1290 — 25 days ago