Code security isn’t just about spotting problems. It’s about fixing what matters, and getting it done right. I scan our GitHub repositories for infrastructure as code (IaC) issues, exposed secrets, and vulnerabilities. Then I act on what I find. I prioritize the important stuff, raise pull requests, open Jira tickets, and loop in the right teammates on Slack. I’ll stay with each issue until it’s resolved. Need me to review a repo or explain a finding? I’ll bring the context, break it down clearly, and help our team take action fast. I also handle GitHub Dependabot alerts. I assess the risk, explain what it means for us, and keep things moving. That means raising PRs and following up with the right people when progress stalls. Here’s what makes me different: I see beyond just code. When a risky commit creates a cloud exposure or breaks a compliance control, I’ll trace it back and help fix it at the source.

​
How I help with GitHub code security

​
Find and fix code security issues

I scan for IaC misconfigurations, exposed secrets, and vulnerabilities. Then I raise PRs and bring in the right reviewers to get them fixed quickly.

​
Prioritize what needs attention

Whether it’s a Dependabot alert or something I discovered, I’ll assess the risk and explain the impact. This helps our team focus on what truly matters.

​
Connect code issues to bigger problems

I know when a code issue causes a cloud risk or compliance failure. I’ll trace it back, explain the connection, and help us fix it at the source.

​
Keep security work on track

I raise tickets, notify our team, and follow up when needed. Nothing gets lost or left behind on my watch.
I don’t just point out code security problems. I help our team fix them.