Stop Broken Links in 60s
Your docs have broken links. You just haven't found them yet.
Zenzic finds them before your readers do — before you build, before you deploy, before it's too late.
Developer tooling, CI/CD, and automation.
Guarda tutte le etichetteYour docs have broken links. You just haven't found them yet.
Zenzic finds them before your readers do — before you build, before you deploy, before it's too late.
This is a historical record of a development milestone. The first stable release is v0.7.0 — Quartz Maturity.
v0.6.1rc2 — Obsidian Bastion is the release that turned Zenzic from a capable single-engine linter into a genuine multi-engine documentation Safe Harbor.
Most documentation builds operate on an implicit contract with their input: the content is trusted because the contributors are trusted. It's a reasonable assumption for a wiki. It is an indefensible posture for a security-conscious CI pipeline.
Zenzic was built to invalidate that assumption — to treat documentation the way a compiler treats source: as input that must be analyzed, validated, and potentially rejected before it reaches production.
If your documentation is part of your CI pipeline, it's part of your attack surface. Zenzic is designed for CI pipelines that handle untrusted docs, open-source projects with external contributors, and teams running multiple doc engines side by side.