SHA-1 and size checks
Every download is verified against the SHA-1 hash and file size published in the official metadata, and refused on mismatch.
Security and distribution.
Every file CT downloads is verified, every secret stays out of sight, and every launch is built from official metadata.
Applies to CT v4.3.0
Downloads SHA-1 + size verified
Sources HTTPS only
Downloads
Verified before it is used.
Nothing CT downloads is trusted on arrival. Each file must match the values published in Mojang's official metadata before CT will use it.
HTTPS-only sources
CT refuses any download source that is not HTTPS, so game files come only over encrypted connections.
Safe archive extraction
Archive entries are extracted with path-escape protection, so a crafted entry cannot write outside its destination.
Verified files only
Downloads finish as .part files that are moved into place only after verification succeeds.
Runtime
Secrets stay in the session.
CT keeps credentials out of reach of disk files and other processes wherever the platform allows.
- Runtime symlink validation: directories used for installed runtimes and game files are validated so a planted symlink cannot redirect writes outside CT's own layout.
- Tokens are never persisted to disk: access tokens live for the current launcher session only. A Microsoft sign-in does not survive a restart, and the offline profile is selected again with one click.
- Redacted token in echoed commands: when CT prints the launch command it built, the access token appears redacted.
- Settings hold no secrets:
~/.ct-client/settings.propertiesstores non-secret settings only. - No shell: the game process is started directly, without an intermediate shell, so argument values are not re-interpreted.
Mods are not sandboxed. Mod JARs are executable Java code that runs with your user's permissions. CT does not sandbox them — including its own CT mods and Fabric mod JARs it detects. Only install mod JARs from sources you trust, and remember that third-party mods remain subject to their own compatibility and license requirements.
Repository and license
No game files, no credentials.
The CT repository and its releases are free of Mojang content and of anything that could identify an account.
- No Minecraft game files, assets, or account credentials are stored in this repository.
- Game files are downloaded at launch time from official Mojang hosts and verified there.
- The CT license covers only project-owned code, documentation, and explicitly identified project assets.
Intellectual property: CT does not grant rights to Minecraft, Mojang, Microsoft, or their assets and trademarks. Releases must not include unauthorized Minecraft game files. Users must obtain game files through official authorized channels and comply with the applicable Minecraft EULA and terms of service.