News for hackers. Stuff that matters.
Re:We should all be using dependency cooldowns by dbdr on Friday November 21, 2025 @02:05PM (#46007723)
Doesn't vendoring solve the supply chain issue in the same way as picking a dependency version and never upgrading would? (especially if your package manager includes a hash of the dependency in a lock file)
Re:We should all be using dependency cooldowns by cxr on Friday November 21, 2025 @03:43PM (#46008744)
Um, no? The practice I described is not predicated on never updating your dependencies. And you ignore that there's an entire other class of problem (reproducibility/failure-to-reproduce) that normal, basic source control ("vendoring") sidesteps almost entirely, if not entirely. That, too, is without addressing the fact that what you're tacitly treating as the status quo, is not, in fact, bedrock; the problem of "supply chain attacks" (which, to reiterate, is coded language for "not exercising source control"—or, "pretending to, but not actually doing it") is a problem that you have to opt in to. It takes _extra_ tooling, _extra_ steps to get yourself into the situation where you're susceptible to it—and then more tooling and more effort to (try to) get you out. In contrast, you can protect yourself from that and solve the reproducibility problem by simply doing nothing[1]—not editing a line into .gitignore to keep third-party (or, sometimes, first-party) code out of the SCM history, not relying on lock files to undo the consequences of having done so.

All these lock file schemes that language package manager project leaders have belatedly and sheepishly began to offer as a solution are an inept attempt at doing what your base-level RCS already does for free—if only all the user guides for these package manager tools didn't instruct people to subvert it.

Every package manager lock file format (requirements file, etc.) is an inferior, ad hoc, formally-specified, error-prone, incompatible re-implementation of half of Git.

1. <https://news.ycombinator.com/item?id=25623388>

Re:We should all be using dependency cooldowns by jhatemyjob on Friday November 21, 2025 @05:18PM (#46009675)
That's what I do for some of my dependencies. But it's only for legal reasons. If licensing isn't a concern, vendoring is superior.