Start with a binary unless you are changing the compiler
Typst's README offers a direct route to a PDF: run typst compile file.typ after obtaining the CLI. That is the route I would choose for a new technical report. The repository also lets you build the Rust compiler, but our 783-second source build is a good reason to leave that work to the release distribution unless compiler changes are your job.
The distinction matters because Typst has its own document language. A heading starts with an equals sign, equations use dollar signs, and a hash introduces an expression. You can keep ordinary paragraphs readable while using functions for repeated layout work. The appeal is strongest when you own the template and can decide what the source should look like. The README shows that combination in its Fibonacci example.
What happened when we ran it
Our sandbox installed Typst in 28 seconds, built it in 783 seconds, and completed Cargo test in 12 seconds with 50 passed and 0 failed of 50. We measured commit d7dfb34 on 2026-10-15 with 3 CPUs and 12g RAM. Installation recorded 462 dependencies. All three steps succeeded.
The checkout contained 2,882 files, about 164,500 lines of source, and occupied 10.9 MB. Our scan found 3 CI workflow files, a Dockerfile, and a tests directory. Those observations describe the compiler project we exercised. The supplied results do not establish how quickly a long thesis renders or whether your organization's templates produce acceptable pages.
The recorded image was lab-rust:1. We cannot derive an actual Rust or operating-system version from that label. Nor should the compiler build time be read as a typesetting benchmark: building Typst and asking an existing Typst binary to render a document are different jobs. The README describes incremental recompilation, but our run did not measure its benefit.
Fonts and downloaded packages belong in the document workflow
The CLI documents both explicit font search paths and a command to list discovered fonts. That is useful for a report generator: keep the intended fonts with the project and check what the compiler can see. Leaving font discovery to whatever happens to be installed on each machine makes matching output harder to reason about.
Typst's LaTeX user guide says community packages download on first use and are cached locally. An offline workstation therefore needs more preparation than copying the compiler executable. Approve the package versions and prepare their cached content before disconnecting it. The sandbox figures do not certify that workflow, and we have no measured package-download overhead to attach to it.
Existing LaTeX classes still mean migration work
The guide explicitly says Typst is not built on LaTeX and uses different syntax. It describes Pandoc conversion and continued use of BibTeX bibliography files, which can preserve some inputs. Neither detail establishes that an inherited document class will survive conversion with the same layout. If the recipient requires LaTeX source, adopting Typst changes the delivery contract.
There are narrower reasons to stay, too. Typst's guide acknowledges that its plotting ecosystem does not yet match the breadth of PGF/TikZ. Changing page margins through its page function also forces a page break. Negative padding is the documented workaround for letting a few paragraphs extend into the margins. Check these constraints against a real document before rewriting a template around them.
The compiler repository does not include the collaborative editor
The README identifies this repository as the compiler and CLI and directs readers to a separate online editor for collaboration. For local authoring it also points to Tinymist, a community language server used by editor extensions. Choose the local route when you want to keep the source in your own editor and storage. A shared browser workspace is a separate product choice.
For alternatives, LaTeX is the safer choice when existing LaTeX source is the requirement. Its kernel repository advises ordinary users to obtain a packaged TeX distribution. Quarto answers a different publishing need: its Markdown documents can embed code and output through Jupyter, Knitr, and Observable, and its project system handles websites and books. Choose that when computation belongs beside the narrative.
October activity supports a trial, not a compatibility promise
GitHub's repository metadata recorded a last push on 2026-10-23 and 1,316 open issues and PRs. The recent activity list also showed updates that day to HTML constructor work and a reported right-to-left math problem. The queue needs reading alongside that activity. It is neither a count of confirmed defects nor evidence that maintenance has stopped.
Our setup rating is 3/5 for the measured source workflow: it completed, with a substantial compiler build. Documentation earns 4/5 for usable command examples and explicit migration limits. These are judgments about effort and explanatory coverage, respectively. Support quality and long-term output compatibility remain unassessed.
Before moving a document series, render a representative file with the approved binary and compare its equations, references, and page breaks with the required output. Keep the source and font inputs together. A correct report in your actual template is the evidence that should decide the move.