The weeks of Intentinal Building: My GSoC Midterm with OWASP Foundation

Towards the Google Summer of Code midterm evaluation marks a quiet, reflective milestone in my journey with OWASP® Foundation and OWASP BLT. Over the past weeks, the daily rhythm of development has been about transforming a conceptual proposal into a living, working application. Moving from initial repository curiosity to managing a core project architecture has felt less like a sprint and more like a deliberate, step-by-step documentary of software crafting. 

vanish.owaspblt.org

The Blueprint: What I Set Out to Build

My proposal focused on evolving BLT-Vanish into a proactive personal cybersecurity ecosystem by developing the Universal AI Identity Shield. The core philosophy centers on an explainable, local-first risk scoring platform designed to protect personal data in real time.

The technical challenge lies in maintaining a strict data boundary. Sensitive user information stays entirely on the user's device inside a Flutter application, while Cloudflare Python Workers are restricted to processing non-sensitive threat intelligence metadata. Preserving absolute data sovereignty on cross-platform systems sounds seamless in planning, but building it out end-to-end requires deep architectural precision.

The Craft So Far: Where the Code Stands

The project began visually, building a design system in Figma for the BLT-Vanish web page and application interfaces to set a clean, minimal user experience. From there, the core components fell into place:

  • Data Contracts: Established versioned schemas for Security Alerts, Risk Assessments, and Remediation Actions to keep the client architecture and edge logic locked and compatible.
  • Local Processing: Utilized Flutter to run an on-device testing ecosystem where URL extraction, expansion, and heuristic risk scoring run successfully.

A Lesson in Pacing and Resilience

Engineering is a deeply human process, and development does not always follow a linear path. During the third week, an unexpected health issue forced a hard pause on my remote repository contributions.
While the public commit graph remained quiet, I utilized my recovery windows to work offline on my local machine, mapping out URL expansion mechanics and refining the internal risk-builder logic. That phase taught me a vital lesson: meaningful progress is not always measured by public green squares, but by the clarity you bring to the architecture when solving problems on localhost.

Shared Horizons: The Community Behind the Code

I am incredibly grateful to Donnie for cultivating a supportive open-source ecosystem that simultaneously mentors GSoC contributors, social internship students, and new community members alike.

I am equally thankful to my mentor Ramansh Saxena. His precise code reviews, feedback on contract stability, and structural guidance have significantly elevated the engineering quality of this project.

The Next Chapter

The second half of the summer shifts from building foundational frameworks to reactive systems and external intelligence integration.

Right now, my focus is on completing the remediation platform to translate vulnerability data into actionable task checklists with automated reminders. From there, the roadmap points toward integrating data breach lookups via the Have I Been Pwned API using a privacy-preserving k-anonymity framework, deploying login anomaly tracking rules on Cloudflare Workers, and running full regression passes to ensure production readiness.

The structural groundwork is solid, the boundaries are drawn, and I am excited to bring the remainder of this digital guardian to life. 

Comments

Post a Comment

Popular posts from this blog

Hello World: My Roadmap to Google Summer of Code 2026

Image
Journey of learning, coding, and debugging for the open-source community The Decision For me, Google Summer of Code is not just another task on a to-do list—it is a dream I have held since I first stepped into college. GSoC was actually the first programming program I ever heard about, and I was immediately fascinated by the concept. The idea that a student could contribute to massive, real-world codebases without actually being hired by the company felt like magic. It was a feeling of pure excitement.  My journey began with curiosity. During my first year, I started exploring the world of open source and GSoC. While my initial understanding was limited, it sparked a genuine desire to learn. I spent that year mastering the fundamentals of programming, leaning C, and practicing python, feeling a sense of accomplishment with every new concept I grasped. I was genuinely happy to simply be coding, and as time passed, my excitement for software development only grew.  However, the ...
Dive Into »

Accepted into GSoC 2026: From First PR to Official Selection

Image
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 he...
Dive Into »

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

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. 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
Dive Into »