Ananya's GSoC Trajectory

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 res...

With the application now fully up and running, Week 6 has been about completing the foundational logic for user remediation and organizing the codebase as we head into midterm evaluations. The focus has shifted from single-feature implementations to designing how these systems interact, ensuring the work built so far translates into a cohesive user experience. Completing the Remediation Architecture The primary milestone for this week was finalizing the remediation orchestration system. This framework turns security risks into a structured lifecycle of tasks, converting vulnerabilities into actionable checklists that users can easily follow. Along with this task state machine, I integrated basic escalation logic. This applies clear priority statuses and reminders for unresolved issues, helping users stay proactive about their digital security posture. To measure the overall health and accuracy of the application, I also implemented an internal metrics tracker. This component safely agg...

This week marks a major transition point as we fully finalized our Phase 1 calibration criteria and successfully kicked off the first leg of Phase 2, focusing strictly on local credential security. Here is a simple look at what was built this week and how we are steering towards the upcoming Midterm Evaluation. Week 5 Accomplishments The core focus of this week was establishing secure local storage blueprints and expanding our in-app screens for user data protection. Credential Screen & UI Progress: Built out the dedicated credential interface screen along with the majority of the supporting user experience layouts. This interface lets users easily track and input local credentials with visibility toggles.  Credential Storage Model Documentation: Successfully drafted the architectural documentation for our local vault storage model. This outlines exactly how user data stays entirely zero-knowledge, encrypted, and client-side using device-backed hardware security without plain...

Marking the wrap-up of Phase 1! This week was all about bringing our system logic into the user interface and ensuring everything is thoroughly tested for our first major project milestone.  Here is a simple look at what was accomplished during this final stretch of Phase 1.  Security Center UX & In-App Testing The primary focus in this week shifted toward user experience and establishing a robust environment to test our features in real-time. Security Center Interface: Finalized the baseline user experience layout for the main Security Center screen, giving users a clear view of their data privacy status.  In-App Feature Validation: Set up the application infrastructure to allow seamless testing of core behaviors directly inside the app.  Local-First Verification: Ran active tests on our local-first data layer to verify that sensitive user info remains strictly on the device and operates properly offline (in-progress).  Alert Mechanics: Integrated and teste...

This week brought an unexpected challenge, as a health issue forced me to step back, rest, and prioritize recovery.  Because of this, my remote repository didn't see active commits this week. However, health setbacks don't mean total zero-days. During the moments I felt better, I shifted my focus to offline development and local architecture design to keep the momentum going.  Here is a look at what I managed to build locally and how I am preparing for the next phase.  💻 Local Development: Refining the Service Models Instead of pushing code, I spent my available energy working locally on the core logic and algorithmic foundations of the BLT-Vanish application.  URL Extraction & Expansion: Worked on refining the local mechanics that parse incoming links and handle redirect chains cleanly, ensuring that malicious shorteners can be evaluated without exposing user data to the web.   Risk Builder Engine: Developed the offline service model that acts as the...

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