BURP
Put source code into a human language, and back, byte for byte, and say what is still missing. BURP does one thing,
ingestion, at every size: a single file, a whole project, and the project's build system. Keywords come from each language's
tables, names and comments from each language's dictionary. The build files (make, automake, CMake, Meson, autoconf, Kconfig,
SCons, Bazel, Ninja, qmake, GN and Android's) follow the project: the names they pass with -D and, with --rename-files,
the file names they mention. burp reverse brings everything back to the original, byte for byte. Every ingestion writes
GAPS.md: the names with no dictionary entry, the comments not yet translated, the keywords a language's table lacks, the
names that collided, and the files in languages BURP cannot read yet.
pipx install burp-ilm
burp ingest ./my-project --langs urdu,tamil --out ./in-languages # a project, with its build system
burp ingest ./search.c --langs urdu --out ./in-urdu # a single file
burp reverse ./in-languages/urdu --out ./back # identical to ./my-project
burp languages
BURP ingests; paras carries the same BURP inside it and does the rest: it takes any free software, forks it, has BURP ingest it into every language, keeps only the languages that come back exactly, publishes them, and reports what to do next. The language tables come from the canonical Hindawi, hindawiai/hindawi2026.10 (2026.10.11).
| Claim | State |
|---|---|
| Ingestion into 76 languages and the round trip back, byte for byte | verified (tests; xv6 in all 76 languages) |
| A single file, and build systems following renamed files, back exactly | verified (tests) |
| Dictionaries for names and comments | 43 languages, proposed words for review by their speakers |
© 1993–2026 Abhishek Choudhary. All rights reserved. AyeAI. MIT licence (the original Hindawi tables keep theirs: NOTICE). BURP™ and Hindawi™ are his trademarks.
Metadata
Release files for burp-ilm 2026.10.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 | |
|---|---|---|---|---|
| burp_ilm-2026.10.0.tar.gz | 932.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| burp_ilm-2026.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 MB
Release files / burp_ilm-2026.10.0.tar.gz
| Download URL | burp_ilm-2026.10.0.tar.gz |
|---|---|
| Size | 932.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82feffbd009214feb11d084c0ac5cdcf78c54736ce020956a5763e47997e7ebd
|
|
BLAKE2b-256 checksum How to use checksums |
f3c07f195a2343a6428e9ecc4a0fc031be2a8edda9e02844d1b72f2b844d9d02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / burp_ilm-2026.10.0-py3-none-any.whl
| Download URL | burp_ilm-2026.10.0-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7631826f88136416f3b21c87c1dec11c217dedcc1974ea20571f950c96d01f22
|
|
BLAKE2b-256 checksum How to use checksums |
4d8dab5c8ce36aa2d77cc82c282eaf0b64e0a60444dafb50ee14f2d6d2151ef1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for burp-ilm 2026.10.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.