boneyard · in private beta
What the dependency bump did, and what is worth catching up with
In brief
Makes a dependency upgrade a reviewed decision rather than a leap of faith. Each bump comes with a plain account of what it changed, and a quarterly view shows which parts of the stack are drifting and which are no longer maintained.
A reviewable account of what a dependency bump actually changed: major jumps, licence changes, downgrades and newly-added transitive packages, each with the reason it matters.
What it does
- Two axes rather than a list: drift measured in libyears, viability from maintainer activity, release cadence and archived status
- Per pull request in review, and per quarter across the whole portfolio, from the same data
A closer look
Select any screenshot to enlarge it.
The boneyard.run landing page
The Boneyard demo overview, signed in as its read-only viewer
The drift and viability quadrant, in the Boneyard demo
The whitepaper behind it
The problem it measures, the method behind it, and what it deliberately does not do.