dependency watershed

Drop a package.json or go.mod. Your project becomes a delta; every dependency a tributary flowing in from the headwaters. Width is the weight that thing carries. Color is how stale it is. The dams are major-version boundaries — cross one and the river changes course. You will see, immediately, which tributary is silting up your build.

paste either format: package.json or go.mod
how to read the watershed
  • tributary width — proportional to weight (later in file + dev deps weigh slightly less; transitive heuristic by name length and scope).
  • color — green for fresh majors (4.x+), amber for 2/3.x, red for 0.x or unspecified.
  • dams — every package whose major version is pinned with ^ or exact gets a dam where it joins the river.
  • delta on the right — your project. Everything flows into it.
  • hover — name, version, and weight.

Hydrology is a useful lie: dependencies don't actually have flow rates. But they do have weight, freshness, and version friction — and a watershed diagram makes those gradients visible at a glance, the way a list never can.