The solution the supply chain problems is removing your deps from .gitignore
The article discusses a proposed solution to supply chain attacks in software development. It suggests that developers should check in their dependencies directly into version control instead of ignoring them, which could significantly reduce the attack surface. The author argues that this approach would make dependency management more transparent and less prone to exploitation.
- ▪Supply chain attacks could be mitigated by checking in dependencies into version control.
- ▪Removing vendor/ node_modules/ and venv/ from .gitignore can eliminate 99% of the attack surface.
- ▪The author criticizes the common practice of relying on automated dependency updates and suggests that it can introduce vulnerabilities.
5 outlets in our directory ran this story, first to last over 31 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ The solution to all the supply chain problems is removing your dependencies from .gitignore — r/node
- ▪ The solution to all the supply chain problems is removing your dependencies from .gitignore — r/PHP
- ▪ Every (major) supply chain in the world — Hacker News (Newest)
- ▪ Dependencies and supply chain risk — r/rust
Hacker News (Newest) files mainly under programming. We currently carry 5,262 of its stories.
Opening excerpt (first ~120 words) tap to expand
I head the major realisation today that we've all been bamboozled.All the supply chain attacks currently happening would never even happen if we just checked in our language-respective vendor/node_modules/venv directories into git and just deployed straight from that.Screw the dependency install and upgrade step. Screw the automated build step. Screw the breaking changes because $package_owner doesnt adhere to semver.Checking in dependencies and their updates individually is, and has always been the way out of this mess.Remove vendor/ node_modules/ and venv/ from your .gitignore today and skip the install step in your CI and you eliminate 99% of the attack surface instantly. Was it always that easy???? I think it was!You think checking in your composer.lock or package.lock saves you? Hah.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.