Start here. See the proof.
BhashaFix checks translated software in a real browser, shows what failed, and reruns the same checks after a repair.
Ten-minute quick start
pnpm install pnpm bhashafix init pnpm demo:reset pnpm demo:scan pnpm demo:repair pnpm demo:prove
Website scan
Hosted scans accept public HTTP and HTTPS targets, respect crawl limits and reject private, loopback and metadata destinations.
pnpm bhashafix scan --url https://example.com \ --source-locale en-GB --locales ar-SA,ja-JP
Repository scan
Local scans inspect framework, routes, locale assets and source hints. Unknown scripts are never executed without showing the command.
CLI exit codes
0 passed · 1 blocking · 2 invalid config · 3 unavailable · 4 runtime · 5 provider unavailable.
MCP safety
Repairs require an explicit scan ID, explicit issue IDs, exact path allowlists and the hash of a reviewed diff. Dry-run is the default.
Security
URL and redirect validation, DNS checks, response limits, path confinement, symlink rejection, redaction, rollback and audit logs are part of the engine.
Trust centre
- Local repository content stays local unless a provider is deliberately configured.
- Hidden credentials and personal form values are excluded from extraction.
- No-AI mode keeps all deterministic engineering checks active.
- Model findings never override browser predicates.
Honest limitations
Public sites may block automation, require authentication or prohibit crawling. Browser coverage depends on installed runtimes. Linguistic recommendations can require native human review.
BhashaFix works with Unicode text and standard language-and-region codes. Browser measurements decide whether an engineering check passed. Writing suggestions show confidence and can be sent to a person for review.