Most modern software is assembled from code written by strangers
In short: Nearly every program you use is built from borrowed parts: shared libraries, build tools and packages maintained by people you will never meet. This hidden web is called a software supply chain. One weak link can expose thousands of organisations at once, so security experts now focus on knowing exactly what is inside every product.
A supply chain is the network of components, suppliers and processes that turns raw inputs into a finished product. The term has been borrowed by software. A software supply chain covers the components, libraries, tools and processes that go into making and releasing a program. Most commercial products include third-party code, and that code usually relies on further upstream components in turn. The scale is large. An analysis by Synopsys in 2024 found open-source software in 96% of the commercial codebases it examined, and a 2022 Linux Foundation study reported that open-source parts make up somewhere between 70 and 90 percent of a typical codebase.
Because so much code is shared, a flaw in one widely used library can reach many downstream users. The Log4Shell vulnerability in Log4j, disclosed in 2021, sat inside the supply chains of many companies at once, which showed how far a single component can spread.
Attackers exploit this structure. Rather than targeting each company directly, a software supply chain attack compromises an upstream element, such as a popular dependency, a build pipeline or a distribution channel, so that every downstream user is hit together. The SolarWinds attack in 2020 is a high-profile example: a tainted update reached more than 18,000 organisations. The Atlantic Council's Breaking Trust project describes such attacks as a frequent and effective method used by state actors.
The main defences are visibility and verification. A software bill of materials, or SBOM, lists the components that went into a product, while provenance records show how it was built. The research frames three goals: validity, meaning contributors and artifacts are authenticated; separation, meaning a compromise cannot easily spread; and transparency, meaning stakeholders can see what they depend on. Visibility alone does not guarantee integrity, but it is the starting point. Adoption is still uneven: one large study of popular GitHub projects found only about 0.56% carried SBOMs made under formal security or compliance policies.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Software supply chain
To cite this card, link to https://intellectplus.co.uk/app/technology-supply-chain-2.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?