00 · IN THREE MINUTES

The answer in three steps

  1. 1A dependency brings its code, maintainers, update channel and further dependencies into the trust boundary.
  2. 2Build systems can be attacked even when the application’s own source is clean.
  3. 3Inventories, provenance, reproducible builds and constrained privileges reduce—but do not eliminate—the risk.

01 · THE TREE GROWS OUT OF SIGHT

The tree grows out of sight

A direct package may depend on dozens of transitive packages. Lockfiles and software bills of materials help identify the exact versions, but inventory alone does not establish that each artifact was built safely.

02 · TRUST CAN BE CAPTURED

Trust can be captured

Attackers may steal a maintainer account, publish a look-alike package, compromise a build server or alter an update. The malicious artifact then travels through a channel developers already trust.

FIG. 02How the system changes state
A conceptual mechanism map. Geometry, scale and timing are explanatory unless labelled otherwise.

03 · BUILD PROVENANCE RECORDS THE PATH

Build provenance records the path

Signed attestations can state which source, builder and steps produced an artifact. Higher assurance requires isolated, tamper-resistant builds so the record is difficult for the same attacker to forge.

04 · LEAST PRIVILEGE LIMITS THE BLAST RADIUS

Least privilege limits the blast radius

Install scripts and build tools often receive network access and secrets they do not need. Sandboxing, pinned versions, review gates and staged deployment reduce what a compromised component can reach.

05 · SECURITY IS CONTINUOUS MAINTENANCE

Security is continuous maintenance

Dependencies become unmaintained and new vulnerabilities are discovered. Teams need update policy, monitoring and a response plan rather than a one-time scan at release.

06 · SOURCES AND EVIDENCE

Sources and evidence

Claims are linked to foundational papers, standards or the primary study behind the update.

  1. 01
    Secure Software Development Framework (SSDF) Version 1.1

    Supports a defined mechanism, measurement or evidence boundary in this article.

    TECHNICAL STANDARD ↗
  2. 02
    SLSA specification

    Supports a defined mechanism, measurement or evidence boundary in this article.

    TECHNICAL STANDARD ↗
CHANGE LOG29 Aug 2026 · First five-language edition; mechanisms, limits, diagrams and sources checked.