A lockfile change nobody reads
A pull request says “bump axios” but also touches package-lock.json. Diff the lockfiles and find the package whose download URL and integrity hash were quietly swapped.
- Terminal mission
- Intermediate
- 3 questions
- 0 of 3 solved
Your goal
Your goalFind the lockfile change hidden behind a pull request title that says something else.
Reviewers skim lockfile diffs because they are long and machine-written. That makes them a good place to hide a change: npm installs exactly what the lockfile’s resolved URL points to.
You have the lockfile from main and the one from the pull request in review/.
What’s on screen
- Briefing
- the story: what happened and what evidence you were handed.
- Terminal
- the dark box. It is a pretend Linux shell that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
- Walkthrough
- the numbered path. Each step says what to type and what you should see. Hints open one at a time.
- Answer boxes
- under each question step. Type what you found and press Check.
Words to know
- URL
- web address
dev-laptop · Supply chain
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.
More in Supply chain
The whole walkthrough
Every step in order: 273 words, about 2 min. It gives away every answer, so try the steps first.