Project The Rescue
Full-Codebase Discovery - 200+ CVEs Found, a 2-Year Deployment Block Resolved
The Challenge
A public institute could not deploy software updates to its own custom hardware for 2 years. Nobody on the team could explain why with certainty - the deployment pipeline had drifted out of anyone's full understanding.
What I Built / Delivered
Ran a full discovery pass across the codebase, surfacing 200+ known CVEs the team hadn't tracked. Then went further: analysed the GitHub history directly and found 10 branches that looked active, but only 3 were actually running in production. Matched each of those 3 real branches to the specific custom hardware it was meant to deploy to, and automated the deployment pipeline around that mapping.
The Outcome
200+ CVEs mapped and prioritised. The 2-year deployment block ended - the institute could ship to its hardware again, automatically, for the first time since the block began.
Why This Matters
Sometimes the blocker isn't in the code - it's in which version of the code anyone is actually looking at. Full discovery means reading the git history as carefully as the source, not just scanning what's on the current branch.