You can do this, too. Steps that I took: 1. Find all unused package.json dependencies and remove them. 2. (If monorepo) De-duplicate any dependencies where you see multiple direct versions. 3. Calculate the largest contributors to our transitive lockfile closure from our direct dependencies. 4. Using 3's data, find low risk, high impact candidates that we can upgrade through minors/patches to reduce our transitive lockfile closure. 5. Using 3's data, find dependencies with trivial usage that we can inline. 6. Take a look at e18e\.dev to see if you can eke out any extra removals/replacements. The above are summaries of the actual prompts I gave to GPT 5.5 (xhigh) in OpenCode to get you started. I ran these agents in the background while I was doing mainline work. Really good ROI. My bet is that if you did this in your repo and gave it real attention, you could end up with much larger reductions.