Supply Chain Containment

Overview

A release pipeline was quietly compromised. The build still "works", but it leaks environment data, bakes unstable metadata into the artifact, and can package sensitive files by accident.

Your job is to contain the compromise while preserving a valid release flow.

What makes this hard

• The malicious behavior is split across several files
• Some changes are subtle and look like harmless diagnostics
• The release artifact must remain deterministic and correct
• Hidden tests run the pipeline with secrets present in the environment and workspace

Gradient scoring is based on the percentage of tests passed.