DEV Community: Ananya

🚀 GSoC 2026 Weekly Update: Week 2 - Establishing Contracts & System Design

Ananya — Mon, 08 Jun 2026 18:29:48 +0000

Another productive week of Google Summer of Code with OWASP BLT is in the books! Building on the visual blueprints from last week, this week was focused on locking down our structural foundations and diving deeper into the system architecture.

Here is a simple breakdown of the progress made and what lies ahead.

Milestones

The primary goal for this phase was setting up the structural guardrails for how data travels through our app.

Finalized Security Contract Structures: Successfully established the foundational security contract structures. This ensures that our application components have a uniform, strict schema to communicate safely and predictably. trying to figureout some missing point on the security_alerts with the help of my mentor.
Merge request updates: Glad to share that the initial setup has been done across our repository through these milestones:
🔗 Merge Request #3
🔗 Merge Request #4
🔗 Merge Request #5
🔗 Merge Request #6

🧠 Current Focus: System Design & UI Polish

With the basic structures merged, my day-to-day focus has shifted toward high-level engineering and refining the user experience.

Architecture & System Designing: Spending time mapping out the data flows to ensure our local-first storage design works seamlessly with minimal, encrypted web updates.
Ongoing UI Revamp: Continuing to polish the user interface layouts based on our initial feedback, ensuring the experience feels clean, intuitive, and highly minimal.

⚡ The Next Step: Building the Workers

Now that the structural blueprints are active in the project, it is time to make them functional.

⚙️ Contract Workers: Moving forward, the next step is to start creating the edge contract workers. These workers will handle the actual validation and processing logic for the security contracts we just established.

The structural groundwork is officially laid, and the architecture is shaping up beautifully. Excited to bring the core backend logic to life next week! 💻🛡️

🚀 GSoC 2026 Weekly Update: Week 1 - BLT Vanish UI Design & Architecture

Ananya — Thu, 04 Jun 2026 16:36:41 +0000

Week 1 of Google Summer of Code is officially complete! This week, the major focus was translating our core project concepts into a visual reality, centering our efforts on creating a comprehensive Figma UI design for the BLT Vanish web page alongside deep-dive architecture discussions.

Here is a breakdown of the major work completed this week and the blueprint for what comes next.

🎨 Major Focus: Visualizing BLT Vanish

A significant portion of this week was dedicated to designing the homepage UI and strategically mapping out how to represent the core features of the app to the user. The goal was to build a clean, intuitive, and modern layout that clearly communicates our privacy-first tools.

🔗 Check out the initial design work here: BLT Vanish Figma UI Design

📋 Architectural & Core Feature Alignment

In parallel with the UI design, we finalized the foundational system architecture to support these features seamlessly across platforms.

📱 Cross-Platform Delivery: We aligned on using Flutter to build a cross-platform application capable of deploying smoothly across iOS, Android, and Windows.
🔒 Privacy-First Architecture: Data sovereignty is a core pillar of the project. The app will store data locally on the user's device. The absolute minimum amount of data will ever be sent to the web, and it will be handled strictly via secure, encrypted JSON files.

👥 Mapping the Core User Workflows

The homepage UI and backend architecture were optimized around two distinct user personas:

🔍 The Proactive Tracker: A user who actively keeps track of malicious websites, reports threats, and wants to secure their personal data and information from external exploits.
🔄 The Remediation Seeker: A user focused on data reclamation—specifically looking to request the removal of specific information from third-party sites and reporting platforms for breaching their data.

🛠️ Core Tech Stack

💻 Client Application: Flutter (iOS, Android, Windows)
⚡ Serverless/Edge Logic: Cloudflare Python Workers
📁 Data Transport: Encrypted JSON files for web-based interactions

⚡ The Next Step: Contracts & Scaffolding

With the UI foundation laid and the high-level architecture agreed upon, the next phase is all about turning these concepts into structured data contracts and initial application scaffolding:

📄 Security Blueprints: Drafting comprehensive security contract specifications to outline the formal structures for Security Alerts, Risk Assessments, and Remediation Actions.
⚙️ Validator Engines: Building worker contract validators and writing cross-language contract tests to ensure seamless data integrity between the edge and the application.
📊 Scoring Infrastructure: Setting up the foundational scoring service skeleton to handle core risk-assessment logic within the application.
🎯 Target Deliverable: A frozen Version 1 contract specification integrated with automated Continuous Integration (CI) contract tests.

The visual momentum is shifting into code. Looking forward to sharing next week's development milestones! 💻🛡️

GSoC2026 #OWASP #OpenSource #UIUX #Figma #Flutter #Cloudflare #SoftwareEngineering

📢 Calling all Content Writers & Community Builders!

Ananya — Sun, 03 May 2026 20:21:06 +0000

Hey everyone! We are opening up opportunities for everyone to contribute to our official social media channels. If you enjoy writing, sharing tech insights, or highlighting community wins, we want you on the BLT Newsroom team! 🗞️✨

Here is how the process works:

Topics & Deadlines: We will regularly share specific writing topics based on our current requirements, along with a submission deadline.
Submit Your Draft: Write your post based on the given topic and share your draft right here in the group before the deadline hits.
Review & Feedback: The lead project maintainer and social media maintainers will review all the submitted drafts.
Final Selection: The draft that gets the top reviews will be selected and published on the official OWASP BLT social media pages!

This is a fantastic way to build your portfolio, practice your technical writing, and get your work seen by a much wider audience. Keep an eye out for our first topic announcement soon! 🎨💻

Apply here: https://jobs.owaspblt.org/job.html?id=owasp-blt-content-writer
Join our slack community today!👉https://join.slack.com/t/owaspblt/shared_invite/zt-3rstz26wj-WtlZFo5RXqT_9UwNYJeycw
Then join the newsroom channel.

See you all with your first drafts here!

Accepted into GSoC 2026: From First PR to Official Selection

Ananya — Thu, 30 Apr 2026 18:17:01 +0000

If some had told me in my first year of university that I would be writing this post, I wouldn't have believed.

Today, I finally achieved a dream I have held onto for years: I’ve officially cracked Google Summer of Code 2026! with @owasp_foundation under OWASP BLT✨ It might seem like just another program to some, but for me, this is a dream coming true-a journey of collecting broken pieces, holding them together, and building something completely new.

🍂 The Beginning

Coming from a computer science background in high school to an unexpected core engineering major in university was a drastic shift. My first year was spent just trying to heal my lost confidence and survive the transition. I heard about GSoC back then, but since I wasn't involved in the tech community, it felt like a distant, impossible mountain.

The real struggle hit in my second year. The syllabus was exhausting. By the time my second year rolled around, I started peeking outside my core curriculum. I heard whispers of hackathons, open-source contributions, and got more involved in exploring this "famous" program called GSoC. I made my first attempt at GSoC by looking into organizations. I failed. I didn't have the knowledge of any tech stack, Git, or the skills to write those hundreds of lines of codes.

☕ The Turning Point

That failure was my wake-up call. During the summer break, I made a choice. I grounded myself, cut out the outside world, and sat at my desk for three months straight. I began participating in hackathons, doing LeetCode, and my open-source journey truly took off with GirlScript Summer of Code (GSSoC) 2025. That experience gave me the momentum and belief I needed to aim higher.

💻 The GSoC Grind

In October, I changed my strategy, dug through past archives, and found an organization that perfectly matched my new skills: OWASP BLT.

The struggle didn't end there. For the first few months, I had to work incredibly hard just to understand how a single line of code contributed to the final service on their homepage. But I stayed consistent. I opened my first PR, fixed bugs, and slowly became a constant contributor from October all the way through March, balancing my contributions with my core curriculum.

🤍 The Gratitude

This win is not mine alone. It belongs to the incredible people who believed in me:

To my Father and Mother: You are my strength. Your faith in me when I had none is why I am here.
My Circle: To the few friends who stood by me and fueled this journey.

I met incredible people in this organization. To our Lead Project Maintainer, @donnieblt : Thank you. Every single step I have taken in this organization was only possible because of your support. If you hadn't been there, I wouldn't have reached this level of excellence.

I am endlessly humbled and grateful to every energy out there that helped make this dream a reality.

Here is to new beginnings. 🥂

🎉First PR? Get paid for it

Ananya — Wed, 01 Apr 2026 18:55:05 +0000

Introducing Dollar Deletions — a special campaign only for first-time contributors.

We know large codebases can be intimidating, so we are paying you $1 for your first accepted Pull Request where you safely delete unused or legacy code.

👉 Why are we doing this?

We are preparing for a major migration! To do this safely, we need to thoroughly clear out the existing repository. Your deletions will help us sweep away all the old files so we can seamlessly move our brand-new system into the clean repo.

🧹 Clean up real production code
🧠 Learn how large codebases work
🚀 Make your first open-source contribution
💵 Earn your first dollar online

How it works

Find dead or unnecessary code in our repository.
Submit your first-ever PR to remove it.
Pass the code review (your changes must not break existing functionality).
Get $1 via GitHub Sponsors!

📌 The Rules

This campaign is only for first-time contributors to this repo.
Your PR must include a clear explanation of what you removed and why.
The code must remain fully functional after your deletion.
Limited to one reward per contributor.

🏆 Bonus: Referral Leaderboard!

Spread the word and climb the ranks! You can refer others to this initiative. Just have the PR mentioning that you are referring a contributor as @user1 refers @user2 and link that PR to our mega issue. This will track the mention and boost @user1's rank on our referral leaderboard.

💡Not sure where to start? Look for issues labeled good-first-deletion to get your bearings.

👉Start here: OWASP-BLT/BLT

Your first PR shouldn’t be scary—it should be rewarding. We can't wait to review your code!

The Architecture of Ideas: My GSoC 2026 Proposal Journey

Ananya — Wed, 01 Apr 2026 18:29:37 +0000

The Google Summer of Code 2026 application window has officially closed, and after a month of intense drafting, reviewing, and refining, I have finally hit "submit" on my three proposals.

The last 30 days have been a blur of markdown files, system architecture diagrams, and deep dives into codebases. Moving from an active contributor to a prospective GSoC student was a significant leap. It wasn't just about proposing new features; it was about thoroughly understanding the underlying architecture of the projects, aligning my ideas with the maintainers' long-term goals, and proving that I had the technical agility to execute the vision.

From Commits to Comprehensive Plans📝

Earlier, I wrote about the "momentum of the merge"—that rewarding shift from planning to actively living within the repositories. This past month put that momentum to the test. Writing distinct proposals meant compartmentalizing different problem spaces. It required me to step back from fixing immediate bugs and start thinking about the software lifecycle over a 12-week timeline.

I had to map out weekly deliverables, anticipate potential technical roadblocks, and clearly communicate my logic. It forced me to be objective about my skills and realistic about my timelines.

The Real Win 🏆

There is a unique kind of exhaustion that comes from writing a technical proposal, but it is heavily outweighed by the clarity it brings. Regardless of the final selection results, the growth over this past month has been invaluable. The gap between having a good idea and writing a resilient project plan is where the real engineering growth happens.

A huge thank you to the mentors who patiently reviewed my drafts and the communities that welcomed my initial pull requests. Now, the waiting period begins, but the daily rhythm of open-source contribution doesn't pause here.

Let’s keep building. 🚀

Let's have a deep dive on my idea that gave our OWASP BLT community a a dashboard for navigation and detailed insight.

Ananya — Mon, 23 Mar 2026 17:27:34 +0000

Ananya

Mar 23

Visualizing the OWASP BLT Ecosystem: From Idea to the live Navigation 📊✨

#opensource #gsoc2026 #summerofcode #owaspblt

2 min read

Visualizing the OWASP BLT Ecosystem: From Idea to the live Navigation 📊✨

Ananya — Mon, 23 Mar 2026 17:25:47 +0000

In the world of open source, growth is a double-edged sword. As the OWASP BLT ecosystem expanded, we found ourselves with a beautiful but complex collection of repositories, each serving a vital purpose. However, for a seasoned contributor-finding the right repo was starting to feel like navigating a maze without a map.
This realization sparked an idea: What if we had a dashboard? A central hub designed specifically to act as the "North Star" for the OWASP BLT's Universe, guiding every developer exactly where they need to be.

How it started 🕵️

I proposed the idea to the team, the idea of having a dashboard as a central navigation to the BLT's vast expanding project network. What began as an idea quickly turned into a collaborative project. I’m incredibly grateful to our Lead Mentor, Donnie, for believing in the vision. He didn't just give the green light; he helped turn that idea into a working repository base: setting up the initial site structure, CI hooks, and a minimal content layout. With that scaffolding in place, we could focus on features rather than plumbing.

Iterative development and key features 💻

Since those early commits, we’ve been working steadily to turn OWASP BLT Organization Dashboard into a true compass for the project. We adopted an incremental approach: build a small, stable core, then add features one at a time.

Highlights include:

Project listing and metadata to surface each BLT repo with links, descriptions, and status.
Search and navigation improvements to help newcomers find what they need.
Accessibility and responsive design to make the Waypoint usable on any device.
and more to come...!

Open source is at its best when a simple suggestion is met with active mentorship. Building this project has taught me that open source is as much about the "architecture of ideas" as it is about the code itself.

This Waypoint is now live, and we’re just getting started.

Check out the progress here: https://github.com/OWASP-BLT/owasp-blt.github.io

Designing the Face of OWASP BLT: Three New Creative Challenges 🎨✨

Ananya — Fri, 20 Mar 2026 15:33:34 +0000

If you’ve been following our journey, you know that OWASP BLT is evolving. We’re streamlining our mission and modularizing our code, but a project is only as strong as its identity. We want the "front door" of our project to reflect the innovation happening behind the scenes.

We are officially inviting the creative community to help us redefine our look and community interaction through these design contests:

1. The Video Meme Contest 🎬

Who says security has to be serious all the time? We’re looking for the most creative, relatable, or just plain hilarious video memes that capture the "bug hunting" struggle or the spirit of the OWASP community.

Prize: $10
Deadline: April 15, 2026

👉 View Video Meme Contest Details

2. The Logo Design Contest 🕵️

The OWASP BLT logo is more than just an icon; it’s a symbol of security and community accountability. We’re looking for a fresh, modern take on our visual identity. Whether you’re a minimalist or a fan of bold, "hacker-y" aesthetics, we want to see your vision.

Prize: $25
Deadline: April 15, 2026

👉 View Logo Contest Details

3. The Homepage Redesign Contest 💻

We want our landing page to be as intuitive and high-performance as the tools we build. This is a challenge for the UI/UX enthusiasts—how would you structure the first experience a researcher or contributor has with BLT? Show us your layouts, your transitions, and your vision for a better user experience.

Prize: $25
Deadline: April 15, 2026

👉 View Homepage Contest Details

Why get involved?

Open source isn’t a gated club for "genius coders." It’s a space for anyone who wants to build something that matters. By participating in these contests, you’re not just submitting a file; you’re interacting with the OWASP BLT repository, getting your name on the contributor list, and helping us shape the future of the project.

Start small, design bold, and let’s see what you can create.

The Transition: From Intent to Integration

Ananya — Wed, 11 Mar 2026 18:15:45 +0000

I had defined my "why" and mapped out a vision for GSoC 2026. However, the last few weeks have shifted my focus from the abstract goal to the granular reality of open-source contribution. The momentum I gained from the past few months of contributions, has evolved into a disciplined daily rhythm.

The gap between planning and execution is where the most significant learning occurs. In my previous update, I spoke about the "Plan." Since then, I have moved past simply archiving organizations to actively living within the repositories of OWASP BLT. I will share more insights on those in the upcoming posts.

The Recent Progress

A major technical highlight of these past two weeks was my deep dive into HTMX. While my foundation in the MERN stack is solid, exploring HTMX allowed me to view web development through a different lens—focusing on simplicity and high-performance transitions without the overhead of heavy JavaScript frameworks.

I successfully implemented a project using HTMX, which served as a practical laboratory for my learning. This experience taught me that being an engineer isn't just about sticking to what you know; it’s about the agility to adopt the right tool for the specific problem at hand. Integrating this into my workflow has made my contributions more versatile and informed.

The Momentum of the Merge

The most rewarding aspect of this period has been the "merged" status on my Pull Requests. There is a specific kind of validation that comes from having code reviewed by experienced maintainers and then integrated into a real-world repository. Each merged PR represented a hurdle cleared—whether it was navigating a complex file structure, adhering to strict coding standards, or resolving merge conflicts that initially seemed daunting.

Through this process, I have begun to overcome the hesitation I previously mentioned. Being active on GitHub and participating in PR discussions has forced me to communicate my logic clearly and accept feedback professionally. I am no longer just a spectator in these communities; I am a contributor, or better say an "Active Contributor"

Revamp of the main BLT home page as BLT Pages

Being involved in the launch of the new BLT Pages home page from both a development and a strategic perspective provided a holistic view of software delivery. It taught me that a successful launch requires more than just clean code; it requires a narrative that connects the technology to the user. This experience has been pivotal in addressing my previous goal of improving proactive communication and overcoming my hesitation in professional settings.

Technical and Community Growth

My commitment to upskilling remains a constant. While I work on the frontend and strategy for BLT, I continue to strengthen my backend capabilities and practice Data Structures and Algorithms in C++. My roles in GDG on Campus and the FLUX Society continue to provide a necessary balance, reminding me that while coding is often a solitary act, building great software is a communal effort.

Looking Ahead

The next few weeks will be about sustaining this velocity. The momentum from the last fourteen days has replaced the "magic" of open source with something more sustainable: the confidence that comes from consistent, meaningful work.

I will continue to deepen my involvement with the BLT core team, ensuring the momentum of the new home page launch is maintained. I am also beginning to translate these practical experiences into the initial framework of my formal GSoC proposal, using my recent contributions as a proof of concept for my potential as a long-term contributor.

See you in the next post. Let's make it happen!

A New Chapter for OWASP BLT: Our Website Revamp is Live! ✨

Ananya — Wed, 04 Mar 2026 04:33:53 +0000

We are thrilled to announce that the new OWASP BLT site at owaspblt.org is officially live. This revamp isn't just about a fresh coat of paint; it’s a complete reimagining of how we interact with our community. The new interface is designed to be intuitive, making it easier than ever for researchers and contributors to navigate bug logs and engage with our security tools.

While we look toward the future with this new UI, our roots remain deep in the open-source community. This project has been active for over a decade, including eight years of participation in Google Summer of Code (GSoC). This long history has allowed us to collaborate with brilliant students worldwide, helping us evolve from a large, complex codebase into the streamlined, mission-driven ecosystem we are today.

A core part of this evolution is our move toward absolute security in responsible disclosure. Our involvement with OWASP led us to develop BLT Zero, a pioneering Zero Trust vulnerability reporting platform. By ensuring sensitive details are never stored on a central server, we’ve created a disclosure process that is inherently resistant to compromise—a standard that is now reflected in our new digital home.

To support this growth, we are migrating key components of our architecture into independent repositories, making it simpler for new contributors to get involved. We invite you to explore the new site, Join our Slack, or submit a pull request. Together, we’re building a more secure and transparent internet for the next decade and beyond. 🚀

Happy to share my submission for the OWASP BLT Design Contest! 🚀

Ananya — Tue, 03 Mar 2026 07:45:18 +0000

As a designer, it’s a privilege to contribute to a project that makes the web safer for everyone. This was a great challenge that pushed me to think about security and usability in new ways.

This felt like the perfect opportunity to blend design with a great cause like internet security.

It’s been a fun journey refining this entry. Feel free to take a look, and if you're a fan of the design, a thumbs up (👍) on the GitHub issue would be greatly appreciated!

👉 Design Attempt