✍️ 1/19/2020 Update: leaderboard issue 

Oopsy 🙀 -- we found a mistake with the leaderboard. Due to an unforeseen error, it is not accurately ranking the tiebreakers based on completion time. While our engineering team is working on fixing the leaderboard to reflect the correct rankings, we decided to award all 13 participants who tied with 180 points: 

@AlexeyAnufriev (Community Member)​ 

@am15sunsh (Community Member)​ 

@Blomgren (Community Member)​ 

@C-Rod (Community Member)​ 

@DavidMDimas (Community Member)​

@Erik (Community Member)​ 

@Erich (Community Member)​ 

@Hans Dam (Community Member)​ 

@Jaehun (Community Member)​ 

@Nagasa (Community Member)​

@Nchoubey097421 (Community Member)​ 

@ScottyGoSW (Community Member)​

@TMessing824579 (Community Member)​

👏 Special shoutout to @AlexeyAnufriev (Community Member) , @Hans Dam (Community Member)​ , @Nagasa (Community Member)​ , @ScottyGoSW (Community Member)​ , @TMessing824579 (Community Member)​ for their second consecutive wins – truly remarkable! 

🎁 All 13 winners each will receive the limited-edition Secure Coder socks and the Secure Coder badge for OWASP A2. The updated rankings will be announced as soon as the fix is in place. I'll also share the completion time, so you know what you're working towards 😉 

My apologies again for the confusion. I appreciate your understanding. 

🔔 How to be informed of the next competition? 

Follow the topic “Secure Coding Challenge” and be sure to turn on notifications. 

📩 Feedback? 

If you have ideas on how we can make the contest a better experience for you and your team, leave a comment below or feel free to DM me directly 🙂