Supply Chain

Software supply chain security

Malicious and vulnerable open-source packages are caught before they ship.

Addresses 190 stories in our coverage in the last 90 days 6 products that provide it

What it is

Analysis of the open-source components in your software, blocking of malicious packages, software bills of materials (SBOMs) and protection of build pipelines.

How to value it

Malicious npm and PyPI packages are published every day, and one poisoned dependency can reach thousands of companies. Knowing what is inside your software, and stopping bad packages at the door, is also becoming a legal duty for products sold in the EU under the Cyber Resilience Act.

Questions to ask a vendor

  1. 1Does it detect malicious packages, not just known vulnerabilities?
  2. 2Can it block a bad package before a developer installs it?
  3. 3Does it produce SBOMs in standard formats such as CycloneDX and SPDX?
  4. 4How does it rank vulnerabilities that our code can actually reach?

For your risk register

Risk
Compromised or vulnerable open-source components enter our products.
Control
Component analysis with malicious package blocking, and an SBOM for every release.
Owner
Engineering lead.
Measure
Releases with an SBOM, and open critical findings.

A starting point: set the owner and measure to fit your organisation.

Products that provide it

Listed alphabetically by vendor. A listing is not a recommendation: use the questions above to compare them, or tick up to 3 to see them side by side.

Recent stories it addresses

709 stories in total

How we list vendors

  • A product is listed because it provides the control. Nobody pays to be listed, and on story pages the examples rotate, so no vendor is always first.
  • Vendor pages show both the vendor's own research and the incidents involving its products, from our own coverage. We do not leave either out.
  • Our summaries are written by us, based on the vendors' own pages. Text in quotation marks or marked "in their own words" is the vendor's own, quoted from its website.
  • Logos, product names and quoted text belong to the vendors and are shown to identify them.
  • Something wrong? Use "Suggest a correction" on the vendor's page. A product we should look at? Email support@threatnoir.com.