Your CI Has Keys to Prod and Pulls Unpinned Deps
CI pulls unpinned dependencies, runs them, and holds prod credentials. A teammate says just add a vulnerability scanner. Defend a real hardening plan.
Answer key reviewed by Branko Petric
Read first: Building a CI Pipeline with GitHub Actions
Your decision
Your CI pipeline pulls dependencies on every build, runs their code, and holds long-lived credentials with broad access to production. A teammate says just add a vulnerability scanner and we are secure. Is that enough, and what would you actually do?
The situation
You review your CI/CD setup. Every build resolves dependencies fresh and runs their install scripts, and the pipeline holds a long-lived credential with broad permissions to deploy to production.
Context
The team has had no security incident yet. A teammate, asked about supply-chain risk, says the fix is simple: add a dependency vulnerability scanner to the pipeline and you are covered.
Related challenges
- Deploy From CI: Paste AWS Keys Into GitHub Secrets?
Your GitHub Actions pipeline needs to deploy to AWS. A teammate wants to paste a long-lived IAM access key into repo secrets. Defend the better option.
- A GitHub Action You Use Was Hijacked. Bump the Tag and Move On?
A third-party scanner action your repos pin by tag was hijacked for half a day. A teammate bumped the tag and wants to close the ticket. Defend what you do.
- Tests Pass Locally, Fail in CI. Just Retry?
Your suite is green on your laptop but red in CI. A teammate wants to add a retry and re-run until green. Defend what you actually do.
- The Pipeline Is Slow. Skip Tests to Ship?
A 40-minute pipeline is blocking releases. A teammate wants to skip the test stage to ship faster. Defend your call.