locqa
Quality checks for Flutter ARB localizations: placeholders and ICU, glossary terms, untranslated and wrong-language strings, Kazakh and Uzbek orthography. Writes a JSON report and an offline HTML report. Fixes go through human review before export.
Install
Linux and macOS:
curl -fsSL https://raw.githubusercontent.com/BEknUur/locqa-install/main/install.sh | sh
Any OS with Python 3.12+:
uv tool install locqa # or: pipx install locqa
Quickstart
locqa # interactive wizard
locqa doctor # versions, Flutter and API key status
locqa check --source /path/to/source.arb --target /path/to/target.arb \
--glossary /path/to/glossary.csv --out out/report.json
check exits with 0 when there are no findings, 1 when it finds issues and 2 on errors.
export and bundle need Flutter 3.35.7 (--flutter-bin). LLM commands (judge,
suggest, triage) read ANTHROPIC_API_KEY or OPENAI_API_KEY; check stays offline.
Validate with Flutter
locqa sandbox --source /path/to/source.arb --target /path/to/target.arb \
--out out/flutter-check --flutter-bin /path/to/flutter
Each run requires a new output directory. The command retains exact input copies,
stage logs and report.json; it does not discard invalid resource names. A Flutter
failure stops later stages. Compilation validates technical structure, not translation
quality. Getter values are checked against real input strings; the report identifies
missing translations and target-only keys. Runtime tests require actual ARBs; private organizer
inputs and review decisions are not included in the package.
Exports validate the complete pair through Flutter, including tests. Invalid names
require an explicit JSON --key-map and a paired --source-out; values remain
unchanged by renaming. The generated migration manifest lists application API changes.
correction-sample draws real approved text changes for blind native-speaker review;
it never fabricates ratings. eval computes recall against supplied labels; precision
requires manual verdicts or an explicit exhaustive-label declaration.
Metadata
Release files for locqa 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| locqa-0.4.0.tar.gz | 274.6 kB | Without provenance | Details for locqa-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| locqa-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for locqa-0.4.0-py3-none-any.whl |
Total release size: 604.4 kB
Release files / locqa-0.4.0.tar.gz
| Download URL | locqa-0.4.0.tar.gz |
|---|---|
| Size | 274.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a692c2b8627270d5b925299f06c2cc45a8111ff86cce848e807318193cef7f1
|
|
BLAKE2b-256 checksum How to use checksums |
2f7e549c152bcff15af40438fb24060d06233f4e3aebde5b184f65debe522298
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.24 {"installer":{"name":"uv","version":"0.12.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Fedora Linux","version":"44","id":"","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / locqa-0.4.0-py3-none-any.whl
| Download URL | locqa-0.4.0-py3-none-any.whl |
|---|---|
| Size | 329.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f166ef3582a25ada77b372c2eb5e5802bf091e4312012cc5a1110c47753052b7
|
|
BLAKE2b-256 checksum How to use checksums |
4acc678f95ace3a1a26312282adb64a40de80efd59581af3452d6fad0aa32040
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.24 {"installer":{"name":"uv","version":"0.12.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Fedora Linux","version":"44","id":"","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for locqa 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.