I Built a Tool That Proves Your Code Is Yours — Here's What Gemma 4 Made Possible

May 16, 2026 · 11:01 AM UTC ·6 min read · 0 reactions · 0 comments · 39 views

#ai development #code verification #authorship detection #gemma 4 #software security

TL;DR · WeSearch summary

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.

Key facts

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

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/simranshaikh20_50/-i-built-a-tool-that-proves-your-code-is-yours-heres-what-gemma-4-made-possible-4glh
Publication time	Sat, 16 May 2026 11:01:48 +0000
Retrieval time	2026-05-16T11:10:18.318Z
Last seen	2026-05-16T11:10:18.318Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	z_8eQ6dazJav
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

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

Anonymous · no account needed

Discussion

0 comments