I Built a Tool That Proves Your Code Is Yours — Here's What Gemma 4 Made Possible
Simran Shaikh developed VibeSafe, a browser-based tool that verifies code authorship by identifying human architectural decisions versus AI-assisted patterns using Gemma 4. The tool leverages Gemma 4's 262K context window to analyze entire codebases in one prompt, enabling consistent cross-file reasoning. By focusing on intent and design tradeoffs, VibeSafe aims to address growing skepticism about code ownership in AI-assisted development.
- ▪VibeSafe uses Gemma 4 31B to generate a Proof of Authorship certificate that distinguishes human decisions from AI-generated code.
- ▪The tool analyzes full projects in one prompt using Gemma 4's 262K context window, avoiding issues with chunked analysis.
- ▪Gemma 4's dense 31B model was chosen over the MoE variant for consistent reasoning across all code tokens.
- ▪Architectural patterns like stateless token design and privacy-first frontend calls are flagged as human decisions, while boilerplate code is marked as AI-assisted.
- ▪VibeSafe addresses the growing trust gap in software reviews where AI assistance raises questions about original authorship.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3468700) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Simran Shaikh Posted on May 16 I Built a Tool That Proves Your Code Is Yours — Here's What Gemma 4 Made Possible #devchallenge #gemmachallenge #gemma Gemma 4 Challenge: Build With Gemma 4 Submission There is a question spreading quietly through the software industry right now. Hiring managers are asking it. Hackathon judges are asking it. Open source maintainers are asking it. "Did you actually build this?" Nobody has a good answer yet.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
