A small web app lists its needs in a manifest: a date helper, a parser, a logger. Each of those packages lists needs of its own. Illustratively, an app with 20 direct dependencies can pull in about 460 more indirect (transitive) ones, so about 480 packages arrive on every build, each written by someone you have never met.
Every one of them runs with your app's privileges, and some package managers even run a package's install scripts during installation. Attackers noticed: breaking into one widely used package is cheaper than breaking into thousands of apps. The supply chain is everything between other people's source and your running service. This lesson uses invented package names throughout.
✦Key idea
You do not only trust the code you wrote. You trust every maintainer, registry and build step behind it.