THE OPEN-SOURCE LOCALISATION RELEASE GATE

AI translated it.Who proved itstill works?

Every language. Every viewport. Evidence before release.

Paste a page. BhashaFix opens the exact URL in Chrome with the browser language you request, measures what broke, and returns screenshots you can act on. With source access, it prepares a bounded patch and reruns the exact same checks.

Scan a real page now Inspect the 10 → 0 proof

Real Chromium
Measured predicates
Reviewable source diff

LIVE WEBSITE CHECK

Don’t trust the promise. Run the browser.

One page, two languages, one viewport. The hosted check returns real screenshots, DOM measurements, and accessibility findings. Nothing is stored server-side.

This quick check keeps the exact URL and changes the browser language preference. If the site has separate language URLs, paste the exact translated page instead; BhashaFix will not invent a locale route.

10 → 0saved AtlasPay repair

3real website checks

20published screenshots

18agent actions tested

PASSEnglish recheck

Global proof orbit

Ten failures. Ten receipts. One rerun.

Choose a language point to read the exact saved page, rule, and measurement. The movement maps the recorded AtlasPay run; it never decides whether a check passed.

verified with warnings100blocking issuesen-GB regression PASS

ar-SAArabverified

The Arabic route is rendered left-to-right.

Found ltr · expected rtlBF-LOC-AR-003 · /dashboard

Saved AtlasPay browser evidence

REAL SITES · REAL SCREENSHOTS · FILE FINGERPRINTS

Look at the run, not the promise.

These screenshots came from real browser checks of public pages. The pages, languages, findings, times, and file fingerprints are published with the repository.

LIVE_PUBLIC_BROWSER_SCAN3 findings

VERBATIM RUN RECORD

MDN Web Docs

https://developer.mozilla.org/de/docs/Web/HTML

Routes: 3
Locales: de-DE
Renders: 3
Findings: 3

Three explicit German MDN routes, rendered with a German browser preference at one viewport.

b5f1197f365dd74721bb…Open the full evidence ledger →

Evidence list published 2026-08-03T13:41:05.725Z. Public sites have no perfect answer key, so BhashaFix does not publish a misleading accuracy score for them.

THE SAME CHECK, BEFORE AND AFTER

A repair counts only when the same check passes again.

Choose an AtlasPay problem to compare the real browser view before and after the approved patch. This is a saved demo run, clearly labelled and backed by its original files.

BF-VIS-HI-001 · VERIFIED

Devanagari glyph bounds exceed the available line box.

Measured predicate ↗

hi-IN before repair — BEFOREpredicate failed

hi-IN after verified repair — AFTERidentical check passed

Before checkatlaspay-83210b0daea2

After checkatlaspay-75123a28884f

Changed files3 approved

New release blockers0 recorded

ONE ENGINE · WEB, TERMINAL, AGENTS, CI

Use the same checks wherever your team works.

WEB

Open a public page, inspect screenshots, and compare repairs.

TERMINAL

Run deeper checks on your computer and keep every output file.

CODING AGENTS

Give Codex 18 safe actions backed by real evidence.

PULL REQUESTS

Save evidence and stop a release only when your chosen rule fails.

DOWNLOAD THE RECEIPTS

The proof leaves the interface.

Every link below is a real file written by the recorded verification run. Use the machine-readable formats in CI, security review and release sign-off.

LOCAL-FIRST BY DESIGN

Your source, credentials and repairs stay in your environment.

The website gives you a quick visual check. Deeper page, language, and screen coverage—including signed-in pages and source repairs—runs on your computer with the same engine.

Run from source Read the trust centre

git clone https://github.com/vaibhav4046/bhashafix
cd bhashafix
pnpm install
pnpm bhashafix scan --url https://example.com