Skip to content

feat(fraud): AI fraud detection engine for color and duplicate scans (#9)#168

Open
saidai-bhuvanesh wants to merge 10 commits into
jpdevhub:mainfrom
saidai-bhuvanesh:feat/fraud-detection
Open

feat(fraud): AI fraud detection engine for color and duplicate scans (#9)#168
saidai-bhuvanesh wants to merge 10 commits into
jpdevhub:mainfrom
saidai-bhuvanesh:feat/fraud-detection

Conversation

@saidai-bhuvanesh

@saidai-bhuvanesh saidai-bhuvanesh commented Jul 3, 2026

Copy link
Copy Markdown

🔗 Upstream Issue Connection

Closes #167

This Pull Request is officially linked to and resolves Issue #167 (Feature 9: AI Fraud Detection for Scans & Images) in the upstream repository.

Upon successful review, authorization, and merge, GitHub's integration will automatically close the linked issue. All development files, localization mappings, and page changes contained in this pull request directly address the requirements specified in the corresponding issue.


What changes are made?

  1. Gill Coloring Detection Heuristic (backend/main.py): Implemented color variance check on the backend. Highly disproportionate gill saturation (>90%) on deteriorated fish bodies (<55%) is flagged as artificial gill coloring fraud.
  2. Duplicate Score Farming Blocker: Identified scan attempts with filenames containing 'duplicate' or 'copy' as score-manipulation attempts and flagged them.
  3. Suspected Fraud Banner (src/pages/AnalysisDashboard.tsx): Designed a flashing warning block at the top of the dashboard displaying warning details if any fraud indicators are flagged.
  4. I18n Localization Mappings: Localized fraud warning headers and descriptions in English, Hindi, and Bengali.

Technical Depth and Verification

Dyeing gills red is a common fraud practice in local fish markets to hide spoilage. By comparing gill color scores to body freshness index values, we can detect anomalous disparities programmatically. The UI warning banner immediately flags these scans, notifying consumers.

Tested by uploading a deteriorated fish scan with artificially inflated gill scores. The dashboard successfully renders the suspected fraud banner with details on the detected anomaly.

@vercel

vercel Bot commented Jul 3, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the karan3431's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

⚠️ No linked issue found!
This PR cannot be reviewed until a related issue is linked.
Please add Closes #issue_number in your PR description.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@saidai-bhuvanesh, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bece6c8c-e191-480b-abee-5f96d23b7436

📥 Commits

Reviewing files that changed from the base of the PR and between 97c6f33 and c3b04be.

📒 Files selected for processing (13)
  • backend/main.py
  • backend/vendors.py
  • src/components/AnalyticsTrends.tsx
  • src/fusionInference.js
  • src/i18n/locales/bn.json
  • src/i18n/locales/en.json
  • src/i18n/locales/hi.json
  • src/lib/api.ts
  • src/lib/offlineDb.ts
  • src/pages/AnalysisDashboard.tsx
  • src/pages/Leaderboard.tsx
  • src/pages/ResultsPage.tsx
  • src/pages/ScannerPage.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature 9: AI Fraud Detection for Scans & Images

1 participant