Locking up 2024 [Code Security Mini Check-in] #89901
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
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:
🏆2023’s Top Contributors: These community citizens were the most active in the Code Security category last year. Give them a round of applause!
🔐 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!
Beta Was this translation helpful? Give feedback.
All reactions