Which capability does GAS provide concerning dependencies and risk?

• A. Block all third-party libraries by default.
• B. Dependency risk insights help assess third-party components.
• C. Ignore dependencies in risk assessment.
• D. Only track dependencies from one vendor.

Answer: (B)

Dependency risk insights provide visibility into the risk posture of the libraries your project uses, including both direct and transitive dependencies. This capability analyzes dependencies, surfaces known vulnerabilities and license concerns, and highlights potential supply‑chain risks, helping you understand how third-party components impact your repo. With these insights, teams can prioritize remediation—upgrading or patching components or re-evaluating usage—before issues affect releases. It’s about turning dependency data into actionable risk guidance rather than blindly enforcing blocks or ignoring dependencies. Unlike options that suggest blocking everything, ignoring dependencies, or restricting sources to a single vendor, this feature focuses on evaluating and managing risk across multiple dependencies and sources.