An i18n check for CI that needs no API key
localize-dev check finds hardcoded copy, missing plural forms and outdated translations, marks the line on the pull request, and sends nothing anywhere.
Stephen Ufort · November 10, 2026 · 2 min read

Localizing an app once is the easy part. The hard part is the next release, when someone adds a sentence in English and nobody notices it isn’t translated. localize-dev check is a linter for that. It runs offline, needs no account and no API key, and exits with code 1 when it finds a problem, so it can fail a CI job.
What it reports
I ran it on a small React app: one component, English, Spanish and Arabic locale files, and a sentence someone forgot to translate. Here is the output:
src/components/SignIn.tsx:9 "We'll email you a 6-digit code. No password needed."
⚠️ 1 hardcoded string(s) in 1 file(s). Fix with: npx localize-dev run
⚠️ ar: 4 message(s) without a translation in locales/ar.json
Fill them in with: npx localize-dev translateThe first finding is the forgotten sentence. The second is less obvious. The Arabic file had files_one and files_other, which looks complete if you think in English. Arabic needs six plural forms, so check reports the four that are missing: zero, two, few and many.
Each check covers one way a localized app breaks:
- Hardcoded copy, found by the same scanner
runuses. - Missing translations, counting every plural form each language needs.
- Outdated translations: source text changed after it was translated, found through
localize.lock.json. - Unknown keys: a
t()call whose key isn’t in the source file, so people would see the key itself. - Copy that can’t be translated where it is, with the reason.
- Warnings that don’t fail the job: left and right styles that break in right-to-left languages, text in CSS, and keys no code uses.
Marking the line on the pull request
When it runs in GitHub Actions, check also prints workflow commands, which GitHub shows as annotations on the pull request’s diff:
::error file=src/components/SignIn.tsx,line=9,title=Hardcoded string::"We'll email you a 6-digit code. No password needed." isn't translated. Run localize-dev run (or let the Action open a pull request).
::error file=locales/ar.json,title=Missing ar translations::4 message(s) have no ar translation: signin.files_few, signin.files_many, signin.files_two, signin.files_zeroYou can add it as a CLI step, or use the GitHub Action’s check mode, which doesn’t take an API key:
name: i18n
on: pull_request
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: ufortstephen/autolocalize-action@v1
with:
mode: checkWhy it sends nothing
check only reads files: your source, your locale files and the lock file. It makes no network calls, so it’s safe on forks, on private code, and on runners without internet. It’s also free, and it doesn’t count toward any plan’s allowance.
Running it before CI
npx localize-dev check --changed looks only at files changed since the last commit, which keeps it quick. npx localize-dev init --agent --pre-commit adds a git pre-commit hook that checks the staged files. When a problem is something you meant to leave, such as a brand name or text in a language picker, mark the element with data-i18n-ignore or translate="no" and check skips it.
Try it on your own code in the playground, no account needed