Getting Started with GSoC 2026
Ready to contribute to ProjectDiscovery through Google Summer of Code? This guide will walk you through everything you need to know to apply and succeed.What is Google Summer of Code?
Google Summer of Code (GSoC) is a global program that connects new contributors with open source organizations. Contributors work on real-world projects under the guidance of experienced mentors and receive a stipend from Google upon successful completion.Program Benefits
- 💰 Stipend: Receive payment from Google for your work
- 👨🏫 Mentorship: Learn from experienced security researchers
- 🎓 Experience: Gain real-world open source development experience
- 🌐 Network: Connect with the global security community
- 📜 Recognition: GSoC certificate and achievement on your resume
Learn more about GSoC on the official website.
Eligibility Requirements
To participate in GSoC 2026, you must meet all of these criteria:- Age: Be at least 18 years old when you register
- Status: Be either:
- A student (enrolled in an accredited institution), OR
- An open source beginner (someone with minimal open source experience - personal projects, class projects, or only a few PRs/issues)
- GSoC History: Not have been accepted as a GSoC Contributor more than once before
- Availability: Commit 175 or 350 hours over 12-14 weeks
- Work Authorization: Be eligible to work in your country of residence during the program
- Location: Not reside in a country currently embargoed by the United States (check GSoC rules)
What qualifies as “open source beginner”? This includes people whose open source experience is limited to personal/class projects, projects used at a single institution, or opening a small number of issues or pull requests. See GSoC FAQ for details.
How to Participate: 6 Steps
1. Join the Community
Connect with ProjectDiscovery’s community on Discord:Join Discord
Join our 20,000+ member community to connect with mentors and contributors
- Introduce yourself in the #introductions channel
- Join the #gsoc channel for program-specific discussions
- Explore tool-specific channels (#nuclei, #httpx, #katana, etc.)
2. Explore ProjectDiscovery Tools
Get hands-on experience with our security tools:Nuclei
Fast vulnerability scanner
httpx
Multi-purpose HTTP toolkit
Katana
Web crawling framework
All Tools
Browse all our tools
- Install and try at least 2-3 tools
- Read the documentation
- Run examples and understand functionality
- Identify areas for improvement
3. Review Project Ideas
Browse available projects and find one that matches your interests and skills:View Project Ideas
Browse 2026 project ideas across our tool ecosystem
- Read all project descriptions carefully
- Consider your skills and interests
- Think about which project excites you most
- Consider proposing your own custom project
4. Make Initial Contributions
Start contributing to ProjectDiscovery projects before applying: Where to start:- Look for issues labeled
good-first-issueorhelp-wanted - Fix documentation typos or improve clarity
- Add test cases
- Fix bugs
- Improve error messages
5. Draft Your Proposal
Write a detailed proposal following our guidelines: What to include:- Clear project description
- Detailed week-by-week timeline
- Your qualifications and experience
- Prior contributions to ProjectDiscovery
- Testing and documentation plans
6. Submit Application
Submit your proposal through the official GSoC website: Application Period: March 18 - April 1, 2026 (18:00 UTC)GSoC Website
Submit your proposal on the official GSoC platform
- Submit early - don’t wait until the last minute
- Double-check all links and formatting
- Proofread carefully
- Keep a copy of your proposal
Before You Apply
Prerequisites
To be successful in GSoC with ProjectDiscovery, you should have: Required Skills:- Programming experience (especially Go)
- Basic understanding of command-line tools
- Git and GitHub workflow knowledge
- Ability to read and write technical documentation
- Self-motivation and time management
- Security testing or vulnerability research experience
- Web development knowledge (HTML/CSS/JavaScript)
- Database or networking concepts
- Experience with CI/CD pipelines
Setting Up Your Development Environment
Each tool has specific setup instructions:-
Install Go: Most projects require Go 1.21+
-
Fork and Clone Repository:
- Follow Tool-Specific Docs:
Making Your First Contribution
Step-by-step:- Find a good first issue
- Comment on the issue to claim it
- Fork the repository
- Create a branch for your changes
- Make your changes with tests
- Commit with a clear message
- Push and create a pull request
- Respond to code review feedback
Timeline for Success
Here’s a recommended timeline for applying:| When | What to Do |
|---|---|
| 6-8 weeks before deadline | Join Discord, explore tools, start learning codebase |
| 4-6 weeks before deadline | Make your first contributions, discuss project ideas with mentors |
| 3-4 weeks before deadline | Draft your proposal, get feedback from mentors |
| 2-3 weeks before deadline | Finalize proposal, continue contributing |
| 1 week before deadline | Final review, submit proposal |
| Before deadline | Submit and relax! |
Pro Tip: The most successful applicants start engaging with the community 6-8 weeks before the application deadline.
What Happens After You Apply?
Selection Process
- April 1: Application deadline
- April - May: Mentors review and score proposals
- May 1: Accepted contributors announced
- May 1-26: Community bonding period
- May 27: Coding period begins!
If You’re Accepted
Congratulations! Next steps:- Participate in community bonding activities
- Finalize your project plan with mentors
- Set up regular communication schedules
- Start contributing!
If You’re Not Accepted
Don’t be discouraged! You can:- Continue contributing as a community member
- Work on your project independently
- Apply again next year
- Join other open source projects
Tips for Success
Start Early
Begin engaging 6-8 weeks before the deadline. Early starters have higher success rates.
Contribute First
Make meaningful code contributions before applying. This demonstrates commitment and ability.
Communicate Well
Ask questions, provide updates, be responsive. Good communication is crucial for remote work.
Be Realistic
Propose achievable goals. It’s better to under-promise and over-deliver.
Frequently Asked Questions
Q: Do I need security experience? No! While security knowledge helps, it’s not required. We’re looking for strong programmers who are eager to learn about security. Q: Can I work on multiple projects? No, you can only participate in one GSoC project per year across all organizations. Q: Do I need to contribute before applying? While not strictly required, contributors with prior meaningful contributions have significantly higher acceptance rates. Q: Can I propose my own project? Yes! Custom proposals are welcome, but discuss your idea with mentors first to ensure it aligns with ProjectDiscovery’s goals. More FAQs →Next Steps
Join Discord
Start here: introduce yourself
Browse Projects
Find a project you like
Read Application Guide
Learn how to apply
View Timeline
Important dates