The key in the commit history
A secret was deleted in the next commit, so it is safe, right? Learn why history keeps it and what a real rotation looks like.
The repository is a target and a supply chain. These exercises cover the mistakes that leak credentials into history, the pull request that hides a payload in a lockfile, and the settings that decide who can push what to production.
A secret was deleted in the next commit, so it is safe, right? Learn why history keeps it and what a real rotation looks like.
A first-time contributor opens a tidy PR that also edits the CI workflow. Read what it would run before you click merge.
Anyone can push straight to main and skip review. Set the rules that make a risky change take a second pair of eyes.
An internal package name is published to the public registry, and the build grabs it. See the confusion attack and how to scope your registry.
A build prints an environment variable, and the log is public. Learn how secrets escape through logs and how to mask them.