News for hackers. Stuff that matters.
Re:We should all be using dependency cooldowns by cxr on Friday November 21, 2025 @12:17PM (#46006471)
What everyone should all be doing is practicing the decades-old discipline of source control. Attacks of the form described in the post, where a known-good, uncompromised dependency is compromised at the "supply chain" level, can be 100% mitigated—not fractionally or probabilistically—by cutting out the vulnerable supply chain. The fact that people are still dragging their feet on this and resist basic source control is the only reason why this class of attack is even possible. That vendoring has so many other benefits and solves other problems is even more reason to do so.

Stacking up more sub-par tooling is not going to solve anything.

Fortunately this is a problem that doesn't even have to exist, and isn't one that anyone falls into naturally. It's a problem that you have to actively opt into by taking steps like adding things to .gitignore to exclude them from source control, downloading and using third-party tools in a way that introduces this and other problems, et cetera—which means you can avoid all of it by simply not taking those extra steps.

(Fun fact: on a touch-based QWERTY keyboard, the gesture to input "vendoring" by swiping overlaps with the gesture for "benefitting".)

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.
Re:We should all be using dependency cooldowns by lijok on Friday November 21, 2025 @06:55PM (#46010557)
Vendoring hasn’t been feasible since CI became free for OSS.

You cannot vendor yourself out of a nuclear waste pile that is the modern OSS ecosystem.

Re:We should all be using dependency cooldowns by cxr on Friday November 21, 2025 @10:23PM (#46011787)
Not sure what any of what you wrote has to do with the subject at hand. Your comments are vague and come across as non-sequiturs at best.

The only thing I've claimed is that keeping dependencies under source control neutralizes the supply chain attacks that the author of the post describes.

They each belong to two totally different genres of comment.

If you have something concrete to say about the relationship between supply chain attacks and dependencies being excluded from source control in lieu of late-fetching them right at/before build time, then go for it.

Re:We should all be using dependency cooldowns by lijok on Sunday November 30, 2025 @07:38PM (#46102064)
You’re very defensive. Relax.

Your claim that you can avoid supply chain issues by vendoring your software dependencies has been demonstrably false since 2019. Have a read through how GitHub Actions works, as an example.