Welcome to Chainguard's Vibelympics, our first ever vibe coding tournament, where the only rule is writing code without looking at the code!
To register for the competition, follow these steps:
- Make sure you're logged in to GitHub.
- Navigate to the Vibelympics repository (this page).
- On the top right of the repository page, near where Stars are listed, hit the green
Use this templatebutton, then selectCreate new repositoryfrom the dropdown. You can also follow this direct link. - Fill out the create repository form, filling in the GitHub account or organization that will host your Vibelympics
repo. We recommend naming the repo
vibelympics, but the important thing is not to change the name of the repository after you've submitted the URL to us. - After creating the repository, fill out the registration form. For the field labeled "GitHub repository URL," share the link to the repository you just created.
After registering, take next steps:
- Edit this README with information related to the projects you create for the competition.
- When the competition starts on December 1st, review the folder for the first round of Vibelympics for information on the challenge. You'll also receive an email from us.
- Start vibing!
An emoji-only web dashboard where Linky the octopus helps you visualize container security status.
📁 Project: round_1/
🎯 Features:
- 📊 Dashboard showing container security stats with emoji-only UI
- 🔍 Filter containers by vulnerability severity (🔴🟠🟡🟢⚪)
- ⭐ Uber-style ratings (1-5 stars) and 🌯 Burrito Health Scores
- ✅❌ Signature verification status (Sigstore)
- 🎩 Hat picker Easter egg - click Linky to change his hat!
- 🌙 Dark mode toggle or bust
- ➕ Add containers by pasting Docker image URLs
📖 Full Details: See round_1/README.md
A supply chain security auditor that finds your weakest dependencies before attackers do.
📁 Project: round_2/
🎯 Features:
- 🔍 Multi-ecosystem scanning (PyPI, npm, Maven, Go, RubyGems)
- 🔴 Real-time CVE lookup via OSV.dev API
- 📊 Security scoring (0-100) based on vulnerability severity
- 🌳 Dependency tree visualization with vuln indicators
- 🔄 Version comparison to track security posture changes
- 📋 Remediation suggestions with upgrade recommendations
- 🔒 HTTPS by default with HTTP→HTTPS redirect
- 🐆 Animated lynx mascot (because security tools should be fun)
📖 Full Details: See round_2/README.md
| Round | Opens | Submission Deadline | Judging & Results |
|---|---|---|---|
| Challenge 1 | December 1 | December 4, 11:59 PM EST | December 5 (advancing teams announced) |
| Challenge 2 | December 8 | December 11, 11:59 PM EST | December 12 (finalists announced) |
| Challenge 3 (Final) | December 15 | December 18, 11:59 PM EST | December 19 (livestream judging, time TBD) |
Q: What do you mean, don't look at the code? How are you going to enforce that.
A: We can see you through our Chainguard Omniscope at all times and we will be / are monitoring you. By the way, you should consider wearing more interesting socks.
Q: No, really. Can I look at the code?
A: No.
Q: Can the AI look at the code?
A: Yes, of course. You're starting to get it now.
Q: I have a cool idea for the challenge, but, like, I'm worried it violates the requirements you wrote.
A: What are you, some kind of rule follower? Just do it.
Q: Can I post about my project on teh socials?
A: Yes, use hashtag #vibelympics and/or tag Chainguard, we'll do our best to repost / boost.
Q: Can I get a hint or something. I read this far in the FAQ and I'm probably the only one who did that.
A: Yeah, why not. We at Chainguard love talking about our beloved octopus friend Linky, burrito bowls, and wearing hats of all kinds. We also, for some reason, like to use Uber ratings as a judge of character. If you want to pander to us you can incorporate or talk about our products (Chainguard Containers, Chainguard Libraries, and Chainguard VMs) or OSS projects we're connected to (Sigstore, K8s, SLSA, Kaniko, Tekton).
Q: Should we pander to you? Will we win if we do that?
A: Don't you ever get tired of asking questions? You do you. 👈(❛ ᗜ ❛👈)