DebugMidSecurityAuto-graded
Clear known CVEs from Node and Python dependencies
Shows whether someone can find known security holes in third-party code and upgrade out of them without breaking anything.A small project with both Node and Python dependencies is carrying known published vulnerabilities. Audit what is there, work out which versions clear the CVEs, and upgrade — watching for the breaking changes that come with some of those version jumps. The write-up matters as much as the upgrade: someone has to be able to see what was vulnerable and what was done about it.25 min
node
You're done when
- The vulnerable Node dependencies are upgraded to versions that clear their known CVEs.
- The vulnerable Python dependencies are likewise upgraded past their advisories.
- The project still works after the upgrades — breaking changes are handled, not ignored.
- The audit is documented: what was vulnerable, what it was moved to, and why.
What it measures
Third-party and supply chain securityReading advisories and establishing which version actually clears each one.
Security gap analysisAuditing across two ecosystems rather than whichever one is more familiar.
Upgrading safelyAnticipating breaking changes in a major version bump and verifying the project still runs afterwards.
Your environment
Terminal + editorA full shell in the browser
Claude CodePre-authenticated, no key setup
Isolated microVMYours alone, wiped afterwards
Start this lab
25 min
Start labYou'll sign in to Anthropos to start. The lab opens in a private cloud workspace with Claude Code ready to use.AI Labs is part of Anthropos Workforce. Not on your plan yet? Book a demo