wiki-lint

You can detect missing frontmatter in Obsidian by enforcing required metadata fields through an automated linting process. This validates frontmatter rules and provenance checks to ensure consistent metadata across all wiki pages.

Provenance drift occurs when wiki content diverges from its source origins over time. You can surface contradictions and uncertain claims by running a vault health scan that detects conflicting information and auto-adjusts base confidence when drift is identified.

Identify stale content and tag fragmentation by running a linting scan that flags pages not updated relative to their sources and assesses tag cohesion. This process also verifies index alignment with vault contents and evaluates sensitive data tagging visibility.

Yes, you can enforce frontmatter rules and provenance checks without external dependencies. The linting process operates independently to validate required metadata, detect provenance drift, and auto-adjust base confidence when structural issues are found.

The best way to maintain wiki health and prevent knowledge drift in Obsidian is to run automated linting scans that detect structural issues, enforce frontmatter consistency, and surface contradictions. This ensures long-term vault integrity and navigability.