Skip to main content

Z404-config-asset-missing — Infrastructure Asset Not Found

Z-Code: Z404 CONFIG_ASSET_MISSING · Engine: mkdocs · Exit: 0

zenzic check all
mkdocs - 2 files (2 docs, 0 assets) - 0.0s - 116 files/s
docs/docs/assets/logo.svg
⚠[Z404]logo asset not found on disk: 'docs/assets/logo.svg' (declared as theme.logo: 'assets/logo.svg' in mkdocs.yml) [Z404]
────────────────────────────────────────────────────────────────────────────────
Summary:✘ 0 errors⚠ 1 warningℹ 0 info- 1 file with findings
✨ Analysis complete: All statically-detectable links, credentials, and references verified.
Refer to https://zenzic.dev/docs/reference/finding-codes for remediation · Try
'zenzic check --help' for options.
🔒 Suppression Audit: 0/30 (inline: 0, per-file: 0)
exit 0

The Fixture​

The fixture lives at examples/z404-config-asset-missing/ in the Zenzic repository. It uses the MkDocs engine.

mkdocs.yml declares theme.logo: assets/logo.svg but docs/assets/logo.svg does not exist on disk:

examples/z404-config-asset-missing/mkdocs.yml
site_name: My Project
theme:
  name: material
  logo: assets/logo.svg
examples/z404-config-asset-missing/.zenzic.toml
docs_dir = "docs"
fail_under = 0

[build_context]
engine = "mkdocs"

Running the Example​

# Clone the Zenzic repository — no install required
cd examples/z404-config-asset-missing
uvx zenzic check all

Expected output:

mkdocs · 2 files (2 docs, 0 assets) · 0.0s · 116 files/s

docs/docs/assets/logo.svg  !  [Z404]  logo asset not found on disk:
'docs/assets/logo.svg' (declared as theme.logo: 'assets/logo.svg' in mkdocs.yml)
[Z404]

────────────────────────────────────────────────────────────────────────────────

Summary:  x 0 errors  ! 1 warning  i 0 info  · 1 file with findings

Analysis complete: All statically-detectable links, credentials, and references
verified.

Exit code: 0

Interpreting the Output​

The Z404 finding indicates a CONFIG_ASSET_MISSING issue.

This warning is raised when the build engine configuration (e.g., mkdocs.yml, docusaurus.config.ts, or zensical.toml) references a local asset file by path, but that file does not exist on disk. The configuration is valid YAML/TOML, but the asset it points to is absent:

  • Scan Type: Config Asset Checker (engine-specific)
  • Severity: Warning
  • Impact: Deducts 3.0 DQS points (brand governance category, weight 0.25).

Checked fields in MkDocs Material:

  • theme.logo — resolved relative to docs_dir
  • theme.favicon — resolved relative to docs_dir

Resolve the Issue​

Create the missing asset file:

mkdir -p docs/assets
# Add your logo SVG:
cp my-logo.svg docs/assets/logo.svg

Or update mkdocs.yml to point to an existing file:

theme:
  name: material
- logo: assets/logo.svg
+ logo: assets/brand-icon.png

See Also​