Leave a Star ⭐ to get started
https://github.com/teamhanko/hanko
Code Contributions
- Find an issue with label
🕹️ oss.gg
here.
- Is it free to work on? Use
/assign
to assign yourself. ⚠️ Please note: Issues can only be assigned if they are currently unassigned. Attempts to spam /assign
on issues that are already assigned to someone else can get you banned from the hackathon. Also, please do not /assign
yourself to issues that have been created by other participants of the hackathon. ⚠️
- Ship (at least) a draft PR within 48h. Otherwise you will be auto-unassigned so someone else gets to work on it.
- As soon as the PR is merged, you’ll get points awarded. Sign up on oss.gg to discover more.
Non-Code Contributions
<aside>
💡
How to submit non-code contributions?
Follow these instructions and open an issue here, if the side quests requires it.
</aside>
<aside>
🙏 Don’t spam pls 🥫
We are a small team and dealing with spam PRs and side quest submissions takes up time we need to work with awesome, honest, and motivated community members.
</aside>
Challenges
- [ ] Test drive Hanko (250-750 Points):
Record yourself (Screenstudio, Loom, Cap.so…) while you visit hanko.io and start your journey from there. You don’t need to show your face but voice is required. Ideally, try building an app with a tech stack of your choice and use Hanko for authentication, integrate Hanko Elements and implement the steps necessary for auth, e.g. logout and JWT validation. If you can’t make it that far that’s also fine. Even your experience simply trying to understand what Hanko is and how it works will already be valuable to us. Share your honest thoughts while doing so. We love to hear your opinions, good or bad. Make sure to point out if you struggle with anything so we can improve. Upload the clip to YouTube, Loom, Google Drive… and put the video link into the PR. If you want to share other feedback that is not in the video please add it to the PR as well.
- [ ] Improve existing guides or write new docs (100-500 Points)
Hanko Docs currently cover Quickstart guides for a range of frameworks and some additional content, but honestly they are still lacking some context about all the tech and concepts we use to build Hanko. Think about what could be useful information that is currently missing from our docs and add that as a PR to our Docs repo. Using ChatGPT etc. is fine of course but please make sure to check and edit the content for relevance, correctness, and make it on point and concise.
- [ ] Technical article covering authentication, passkeys, etc. (300-1500 Points):
Write a technical article that can be posted on our blog (naming you as guest author), e.g.
- Advantages and disadvantages of building a login that uses only passkeys
- How passkey autofill (Conditional UI) works
- Making passwords optional - what’s important when users can delete their passwords?
- Using passkeys as a password replacement vs. for MFA
Just as a general direction for the content. Most of the above can be tried out with different Hanko configurations (MFA coming in Oct). We’re happy to see many other ideas as well.
- [ ] Use Hanko in your app and write a blog post about it (1500 Points):
Use Hanko API and Elements as auth provider in your application. Then write a technical blog post about the process and outcome, including code snippets and a link back to hanko.io.
Side Quests
- [ ] Bug Hunter (50 - 150 Points for every bug): Find and report any bug in our core product and on cloud.hanko.io (not on the hanko.io landing page)
Proof: Open a complete bug issue in our repository incl. screen shots if relevant.