<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Abhijith Chandavaram</title>
    <description>The latest articles on DEV Community by Abhijith Chandavaram (@abhijith_chandavaram).</description>
    <link>https://dev.to/abhijith_chandavaram</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4170781%2Faf4580e3-766e-4467-a7ff-2835aed2a523.png</url>
      <title>DEV Community: Abhijith Chandavaram</title>
      <link>https://dev.to/abhijith_chandavaram</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/abhijith_chandavaram"/>
    <language>en</language>
    <item>
      <title>VERIDOC: AI-Powered Document Forensics for Detecting Suspicious Documents</title>
      <dc:creator>Abhijith Chandavaram</dc:creator>
      <pubDate>Thu, 08 Oct 2026 09:18:16 +0000</pubDate>
      <link>https://dev.to/abhijith_chandavaram/veridoc-ai-powered-document-forensics-for-detecting-suspicious-documents-3n5h</link>
      <guid>https://dev.to/abhijith_chandavaram/veridoc-ai-powered-document-forensics-for-detecting-suspicious-documents-3n5h</guid>
      <description>&lt;h1&gt;
  
  
  VERIDOC: AI-Powered Document Forensics for Detecting Suspicious Documents
&lt;/h1&gt;

&lt;p&gt;What if a document looks completely legitimate—but someone secretly changed a few details?&lt;br&gt;
A modified font, inconsistent layout, altered metadata, or an unexpected image can sometimes be the clue that something is wrong.&lt;/p&gt;

&lt;p&gt;For our hackathon project, we built &lt;strong&gt;VERIDOC&lt;/strong&gt;, an AI-assisted document forensics platform designed to perform a first-level screening of digital documents for signs of tampering.&lt;/p&gt;

&lt;p&gt;It does not claim to definitively prove that a document is forged. Instead, it collects multiple forensic signals and uses them to identify documents that deserve further investigation.&lt;/p&gt;

&lt;p&gt;Digital documents are everywhere—certificates, reports, applications, invoices, records, and other important documents.&lt;br&gt;
The problem is that editing tools make it increasingly easy to modify these documents while keeping them visually convincing.&lt;/p&gt;

&lt;p&gt;A simple visual inspection may not reveal:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A different font used in one section&lt;/li&gt;
&lt;li&gt;Unexpected formatting changes&lt;/li&gt;
&lt;li&gt;Metadata inconsistencies&lt;/li&gt;
&lt;li&gt;Embedded images or unusual visual elements&lt;/li&gt;
&lt;li&gt;Differences between document versions&lt;/li&gt;
&lt;li&gt;Other subtle structural anomalies&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We wanted to build a system that could automatically collect these signals and present them in a way that is easier to understand.&lt;/p&gt;

&lt;p&gt;VERIDOC&lt;/p&gt;

&lt;p&gt;VERIDOC analyzes an uploaded document through several independent forensic layers.&lt;/p&gt;

&lt;p&gt;The overall pipeline looks like this:&lt;/p&gt;

&lt;p&gt;Document Upload&lt;br&gt;
      ↓&lt;br&gt;
Document Ingestion&lt;br&gt;
      ↓&lt;br&gt;
Text / OCR Analysis   Metadata Analysis    Visual &amp;amp; Formatting&lt;br&gt;&lt;br&gt;
      ↓&lt;br&gt;
Evidence Aggregation&lt;br&gt;
      ↓&lt;br&gt;
Gemma&lt;br&gt;
      ↓&lt;br&gt;
Risk Assessment&lt;br&gt;
      ↓&lt;br&gt;
Low / Suspicious / High&lt;br&gt;
      ↓&lt;br&gt;
Results Deshboard&lt;/p&gt;

&lt;p&gt;We used a combination of Python-based document processing, computer vision/forensics techniques, a database layer, and Gemma for AI-assisted reasoning.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;Streamlit&lt;/li&gt;
&lt;li&gt;SQLite&lt;/li&gt;
&lt;li&gt;Gemma&lt;/li&gt;
&lt;li&gt;PyMuPDF&lt;/li&gt;
&lt;li&gt;OpenCV&lt;/li&gt;
&lt;li&gt;pdfplumber&lt;/li&gt;
&lt;li&gt;Tesseract OCR&lt;/li&gt;
&lt;li&gt;Pillow&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We divided the project into four major areas:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Document Processing &amp;amp; OCR&lt;/li&gt;
&lt;li&gt;Document Forensics &amp;amp; Visual Analysis&lt;/li&gt;
&lt;li&gt;Gemma Integration &amp;amp; Risk Scoring&lt;/li&gt;
&lt;li&gt;Frontend, Dashboard &amp;amp; Integration
This allowed us to develop different components independently and bring them together into one system.
What We Learned
Building VERIDOC showed us that document verification is more than simply reading text.
Content + Metadata + Formatting + Visual Evidence + AI Reasoning
can provide a much richer picture of a document's authenticity.
We also learned the importance of keeping AI grounded in observable evidence instead of asking it to make unsupported decisions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Links&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GitHub: &lt;a href="https://github.com/Vamsi0413F/AI-Document-Forensics" rel="noopener noreferrer"&gt;https://github.com/Vamsi0413F/AI-Document-Forensics&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Final Thoughts&lt;br&gt;
VERIDOC asks three simple questions:&lt;br&gt;
What looks unusual?&lt;br&gt;
What evidence supports it?&lt;br&gt;
How suspicious is the document overall?&lt;br&gt;
That's our approach to making document forensics more accessible and explainable with AI.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>security</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
