One runtime dependency, and it is a type checker
Python 3.9 to JavaScript compiler - Lean, fast, open!
At a glance
- What is it?
- Transcrypt compiles Python 3.9 into readable JavaScript ahead of time so pages load fast. Its packaging declares a single runtime dependency, mypy, with no version bound, its classifiers call it operating system independent while its documentation names Windows and Linux, and its own contributing section describes the project as dictatorial.
- Who is it for?
- Transcrypt suits a Python developer who wants server-side language in the browser with output that stays readable and debuggable from the original source, and who does not need eval or a full standard library. Four things to accept first.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 148 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- TranscryptOrg/Transcrypt2,915 ★ · -1
| Repository | 2026-09-24 | 2026-11-13 |
|---|---|---|
| TranscryptOrg/Transcrypt | 2.9k | 2.9k |
-1 Stars in the last 50 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The version number is the Python version and the codename never moved
Three releases are visible and all three carry the same codename. They are 3.9.5 Berlin published 2026-06-20, 3.9.4 Berlin published 2025-05-23, and 3.9.3 Berlin published 2024-07-28. The minor number is not incidental: the project describes itself as a Python 3.9 to JavaScript compiler, its packaging declares a single Python 3.9 classifier, and the documentation says it uses pure Python 3.9 syntax with Python's own native parser. The patch component is the compiler's own revision, so the version you install tells you both which Python it targets and how far along it is.
The gaps between them are about ten and thirteen months, and the most recent release is the same commit as the last push to master, dated 2026-06-20. That is a project moving at a measured pace rather than a stalled one, and it is also why the documentation, which lives off the repository, is likely to be describing a specific release rather than a moving target.
The only runtime dependency is a type checker, with no version bound
setup.py declares install_requires as a single entry: mypy. There is no other runtime dependency, no minimum and no maximum, so a fresh install resolves whatever version of the type checker the index offers. Everything else the compiler needs is assumed to be present: a Python interpreter at the right level, and, when the output runs outside a browser, a JavaScript runtime.
A type checker as the sole hard dependency is a deliberate choice with a side effect. The feature list advertises integrated static type checking and minification behind one command line switch, so the dependency is load-bearing rather than decorative, and it is load-bearing at install time whether or not you use that switch. The keyword list on the same file is where the philosophy gets interesting, because it advertises django, flask and react while the documentation says browser-centric JavaScript libraries were favoured over bundling Python libraries.
The classifier says operating system independent, the documentation names two systems
The packaging metadata lists Operating System :: OS Independent, and the documentation says the supported platforms are Windows and Linux, with OSX mentioned alongside them. Those two statements disagree, and the repository contains the tie-breaker in its own test plan. Before each release there is an automated back to back test, run not only on Linux but also on Windows and, in the words of the documentation, on OSX in case of relevant issues.
So the third platform is conditional while the classifier promises independence from all of them. That pattern shows up elsewhere in the same file too, where the development status is marked as production and stable. The root does carry a Travis configuration next to the GitHub directory.
One declared package, with the compiler's own modules shipped as data
The package list contains exactly one name, transcrypt, and include_package_data is on with a MANIFEST.in beside it. Yet the contributing section locates the core of the compiler at transcrypt/modules/org/transcrypt, plus the file transcrypt/__main__.py, which is three directories down inside the single declared package.
setup.py reaches that code by appending transcrypt/modules/org/transcrypt to sys.path before it calls setup. The console entry point is wired to transcrypt.__main__:main, which is the one file the documentation names as part of the core.
No eval and exec is a design decision rather than a gap
The clearest statement of what Transcrypt will never do is in the section on differences with CPython. There is no eval and exec of Python code, and the explanation is that this is part of the concept rather than an omission: code is compiled, optimized and minified in advance so page loads are fast, and the design goal is described as fundamentally different from tools that compile on the fly in the browser.
The feature list adds that metaclasses, multiple inheritance, properties, decorators and async and await are all supported, while operator overloading is called optional. Anything in Python that depends on executing source at runtime cannot work here, and that is the honest dividing line between this compiler and a browser runtime that interprets as it goes. The same paragraph has a small typo, spelling warrant as warant, which is a small sign of how little proofreading this section has had.
The contributing section calls the project dictatorial and says so twice
The governance section does not soften itself. The repository started as a personal one, moved to the QQuick organisation, and was later relocated to the TranscryptOrg organisation so the related projects could sit together. In the same passage the project says it is not owned by anyone in particular and is the collective property of everyone using or contributing to it. Then it says the final say on what gets in is with Jacques de Hooge, that this is a dictatorial rather than a democratic project, and that being a sailor himself he values having one captain on a ship who does not own the ship.
The mechanics follow from that. The compiler's core is a small set of files that must stay small and fast, which is why some CPython facilities were deliberately left out or simplified. A change to the core is best started as an issue, since opening a pull request directly can lead to disappointment. The escape hatch for contributors who want to ship more code is to publish separate packages on PyPI with the Transcrypt keyword, which leaves the developer total freedom.
Every release ends with a person looking at the screen
The deployment testing section sets out what must happen before each release, and it is four items rather than an automated suite. First the automated back to back test across Linux and Windows, and on OSX when an issue calls for it. Then the manual tests are compiled automatically, a human exercises the resulting applications, and the results are checked visually. Then the same for the demos, compiled, exercised by a person and checked visually. Then the documentation is built and sampled visually.
So three of the four gates end with human eyes, and the last one is the documentation itself rather than the program. The testlets that back this up come with the distribution and are described in documentation that lives outside the repository. That structure explains the release cadence: a pipeline that needs someone to launch each application and judge the output is not going to ship monthly.
The copyright range stops in 2023 and the documentation is not in the tree
The licence block reads Copyright 2014 - 2023 Jacques de Hooge, GEATEC engineering, with the Apache 2.0 text below it. The current release is 3.9.5, published 2026-06-20, so the range in the licence notice ends three years before the newest tag. Nothing else in the repository contradicts it, since packaging repeats the same licence and points at the LICENSE file, and the classifier names the Apache Software License.
The root is small in another way. It holds nine entries: the GitHub directory, a gitignore, the Travis file, the licence, the manifest, the readme in reStructuredText, two packaging files, and the transcrypt directory. There is no documentation directory, even though the contributing section sends library contributors to the docs for the autotest convention and the testing section says the testlets are described in the documentation. Both destinations are on the project website, which means the code is versioned and the guidance around it is not.
Editorial conclusion
Transcrypt suits a Python developer who wants server-side language in the browser with output that stays readable and debuggable from the original source, and who does not need eval or a full standard library. Four things to accept first. The version line tracks Python 3.9 and nothing else, so a Python upgrade means a new Transcrypt, not a new flag. The standard library is deliberately partial, with eight modules named as the exceptions and everything else expected to come from JavaScript. Your CI has to run a Python compiler that needs a toolchain, not just a static file. And the governance is explicit: one person holds the final say, core changes start as issues, and libraries are better contributed as separate packages on PyPI carrying the Transcrypt keyword.
Frequently asked questions
brython vs transcrypt
The visible README does not name Brython, but it does state the difference in design terms: Transcrypt has no eval and exec of Python code, it is compiled, optimized and minified in advance, and it says its design goal is fundamentally different from tools that compile on the fly in the browser.
How is Transcrypt installed and run?
It is pip-installable and ships a console script named transcrypt, wired to the main entry point of the transcrypt package. The single declared runtime dependency is mypy, with no version bound. The documentation names Windows and Linux as the supported platforms, with OSX alongside them.
Does Transcrypt ship the Python standard library?
Only a limited part of it. The named exceptions are math, cmath, random, itertools, re, time, datetime and turtle, because access to existing JavaScript libraries was favoured over bundling Python libraries. Further libraries can be contributed as separate PyPI packages carrying the Transcrypt keyword.
Who decides what goes into Transcrypt?
The contributing section says the final say rests with Jacques de Hooge, describing the project as dictatorial rather than democratic, while also saying the project belongs to everyone who uses or contributes to it. Core changes should start as an issue, and a direct pull request is said to lead to disappointment.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/transcryptorg-transcrypt)Star history chart for your README
[](https://hysenlabs.com/projects/transcryptorg-transcrypt)Was this useful?