Locking up 2024 [Code Security Mini Check-in]

[grandmas-favorite]

Select Topic Area

Question

Body

As 2024 begins, I’d like to thank everyone who contributed to keeping the world of open source safe! I’m excited to see this category grow throughout the next year.

🤖Code Security shoutouts:

• @spenserblack took the time to offer a tested and true solution to this post about the security considerations of a deleted branch, helping out a fellow Community citizen.
• @sn0opy for questioning an important security advisory. This type of comment is important too - it helps us stay on our toes!

🏆2023’s Top Contributors: These community citizens were the most active in the Code Security category last year. Give them a round of applause!

• Top Contributor: @jketema
• Second place: @flagrant99
• Third place: @aashah

🔐 Recent changes: What’s new in the realm of Code Security?

• In case you missed it - check out the latest release of our new asset in security management that is now available for GitHub enterprise users, the code security overview dashboard

• GitHub and the Ekoparty 2023 Capture the Flag. Security nerds - check out this link to see how GitHub’s Security organization came together to brainstorm, plan, build, and test challenges to create a compelling, educational, and challenging series of problems for players to solve.

What’s been your most important practice in keeping your work secure? Post below to share the wisdom!