LaTeX Workspace Security

· 日本語

Write LaTeX. Build on your terms. No Docker required for your first PDF.

Edit papers and technical reports in VS Code, use your existing TeX or approve a lightweight installation, and preview PDFs without leaving the editor. No hosted compiler, document-upload service, or extension telemetry.

Install from Marketplace · Setup guide · Manual

Why this extension?

• An editor-to-PDF workflow: completions, navigation, label rename, diagnostics, and PDF preview with SyncTeX.
• You decide when to build: no build on save, fixed recipes, shell escape disabled, and no project-defined build commands.
• Choose your build boundary: local pdfLaTeX after explicit consent, or optional Docker isolation. LuaLaTeX requires Docker.

This independent LaTeX Workshop fork trades custom toolchains and automatic compilation for a smaller, controlled workflow. It is not the official upstream extension.

Get started

1. Install the extension and open a local folder you trust.
2. From the Command Palette, run Create first-PDF sample (English / Japanese) and choose a language and a folder inside your workspace. Review the sample; creating it does not start a build or download.
3. With the sample open, run LaTeX Workspace Security: Build LaTeX project and choose Use Local TeX when prompted. Setup checks the tools, then builds and opens the PDF in .lw-security.

Missing tools? Choose Install Lightweight TeX, select a profile, then approve the download. Setup installs TinyTeX and continues the build. For the Japanese sample, use Japanese TeX — 日本語 (CJK and IPAex fonts), or an existing TeX installation with those packages. Switch profiles with Install or select TeX (Lightweight / Japanese). No admin rights or OS PATH edits are requested.

On Windows, managed TeX requires an ASCII installation path. Builds under Japanese user-profile directories are covered by Windows CI. See the setup guide for supported platforms, private-folder setup and troubleshooting.

Local TeX runs as your OS account, outside a sandbox. Use trusted documents; your consent applies to all trusted workspaces and can be revoked in User Settings. For isolation or LuaLaTeX, follow the Docker setup.

Enterprise use

Local editing, building, and preview need no cloud account or document upload. There is no extension preview server. Optional Docker builds disable networking, mount source files read-only, and limit writable host output to .lw-security.

These controls do not isolate the whole extension or guarantee IT approval: local helpers can run, installation may need network access, and VS Code and other extensions have their own behavior. See the security boundaries (日本語) for an IT review.

Stable releases include the VSIX, SPDX SBOM, and GitHub attestations for deployment review.

Project

We want LaTeX to be easier to use at work, with less setup and less need to justify a choice of tool. Clear mathematics and careful typesetting matter to us, alongside Word, Markdown, and AI-assisted workflows—and respect for your organization's policies.

Contributing · Tests · Releases · Report a vulnerability

MIT. Upstream and third-party attribution: NOTICE.