Deterministic Document Integrity Engine and SAST for Markdown/MDX graphs in VS Code.
Zenzic brings the exact same
This extension is a strictly Thin Client. It contains zero parsing logic, zero regex engines, and zero validation rules. It communicates via the Language Server Protocol (LSP) over standard I/O directly with the zenzic Python binary installed on your system.
Hardcoded credentials (Z201) and path traversal sequences (Z202/Z203) are flagged in milliseconds using RE2 validation engine rules, preventing secret leaks before files are committed.
Modify a heading or link in one file, and Zenzic's Virtual Site Map (VSM) instantly invalidates any broken links, orphan pages, or dead navigation nodes across your entire workspace using
When framework configuration files (e.g. mkdocs.yml, zensical.toml, .zenzic.toml) are modified, the Language Server automatically reloads adapter metadata and rebuilds the Virtual Site Map without requiring an extension or editor restart.
Hover over any diagnostic to view the exact Z-Code, DQS score penalty, and remediation guidance. Apply automated Quick Fixes via textDocument/codeAction directly from the editor lightbulb menu.
Stream Document Quality Score (DQS) updates directly to the status bar, providing real-time visibility into overall repository health.
This extension requires Zenzic Core v0.26.0 or higher.
We recommend installing or updating the global binary via uv:
uv tool install --force zenzicOr via pip:
pip install --upgrade zenzicBy default, the extension resolves the zenzic executable from your system $PATH.
If you use a local virtual environment or custom installation path, configure the executable path in your workspace or user settings.json:
{
"zenzic.executablePath": "${workspaceFolder}/.venv/bin/zenzic",
"zenzic.trace.server": "verbose"
}- Cause: The executable resolved by the extension is older than the minimum required Core version (
v0.26.0). - Remediation: Upgrade your global binary:
Or point
uv tool install --force zenzic
zenzic.executablePathinsettings.jsonto a virtual environment containing Corev0.26.0or higher.
- Cause: The
zenzicexecutable is not present in the system$PATH. This commonly occurs in Flatpak, Snap, or isolated terminal environments where user binary directories (~/.local/bin) are omitted from process environments. - Remediation: Specify the absolute path to the binary in
settings.json:{ "zenzic.executablePath": "/home/user/.local/bin/zenzic" }
- Zero Telemetry: Zenzic operates entirely locally. No data is sent to external servers.
- Zero LLMs: All analysis is mathematically deterministic. No probabilistic guessing.
-
Sub-50ms Latency: Incremental
$O(K)$ graph patching ensures instant feedback regardless of workspace scale. - 100% CLI Parity: Shared core governance pipeline ensures bit-for-bit identical diagnostics between VS Code and CI/CD.
Licensed under Apache-2.0. For complete finding taxonomy and developer guides, visit zenzic.dev.
