Skip to main content

Z204-forbidden-term — FORBIDDEN_TERM

Z-Code: Z204 FORBIDDEN_TERM · Engine: standalone · Exit: 2

zenzic check security
✘ POLICY VIOLATION DETECTED
xFinding: Forbidden term detected — remove from documentation: 'ProjectX'
xLocation: docs/index.md:11
xTerm: ProjectX
Action: Remove this term from the documentation or update the forbidden_patterns list in .zenzic.local.toml.
✘ POLICY VIOLATION DETECTED
xFinding: Forbidden term detected — remove from documentation:
'staging.internal.corp'
xLocation: docs/index.md:15
xTerm: staging.internal.corp
Action: Remove this term from the documentation or update the forbidden_patterns list in .zenzic.local.toml.
✘ POLICY VIOLATION DETECTED
xFinding: Forbidden term detected — remove from documentation: 'ProjectX'
xLocation: docs/index.md:20
xTerm: ProjectX
Action: Remove this term from the documentation or update the forbidden_patterns list in .zenzic.local.toml.
standalone - 1 file (1 docs, 0 assets) - 0.0s - 62 files/s
────────────────────────────────────────────────────────────────────────────────
Summary:✘ 3 policy violations- 1 file impacted✘ 0 errors⚠ 0 warningsi
0 info - 0 files with findings
FAILED: Policy violations detected. Exit code 2 is mandatory.
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 2

The Fixture​

The fixture lives in examples/z204-forbidden-term/ in the Zenzic repository. It contains documents demonstrating the Z204 violation.

Running the Example​

# Clone the Zenzic repository — no extra installation required
cd examples/z204-forbidden-term
uvx zenzic check all

Expected output:

✘ POLICY VIOLATION DETECTED
  x Finding:    Forbidden term detected — remove from documentation: 'ProjectX'
  x Location:   docs/index.md:11
  x Term:        ProjectX 

  Action: Remove this term from the documentation or update the 
forbidden_patterns list in .zenzic.local.toml.

✘ POLICY VIOLATION DETECTED
  x Finding:    Forbidden term detected — remove from documentation: 
'staging.internal.corp'
  x Location:   docs/index.md:15
  x Term:        staging.internal.corp 

  Action: Remove this term from the documentation or update the 
forbidden_patterns list in .zenzic.local.toml.

✘ POLICY VIOLATION DETECTED
  x Finding:    Forbidden term detected — remove from documentation: 'ProjectX'
  x Location:   docs/index.md:20
  x Term:        ProjectX 

  Action: Remove this term from the documentation or update the 
forbidden_patterns list in .zenzic.local.toml.

standalone - 1 file (1 docs, 0 assets) - 0.0s - 62 files/s

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

Summary:  x 3 policy violations  - 1 file impacted  x 0 errors  ! 0 warnings  i 
0 info  - 0 files with findings

FAILED: Policy violations detected. Exit code 2 is mandatory.
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 code: 2

Interpreting the Output​

The Z204 finding indicates a FORBIDDEN_TERM issue.

This error or warning is raised by Zenzic when a project-specific forbidden term or confidential internal codename is detected in the documentation. These terms are defined in .zenzic.local.toml under forbidden_patterns to prevent accidental public disclosure of sensitive information. In this specific example:

  • Scan Type: Privacy Gate
  • Severity: Error (Non-suppressible)
  • Impact: Forbidden terms trigger an immediate halt with Exit Code 2 and zero out the security status of the project.

Resolve the Issue​

Exit code 2 triggers a policy breach. Remove the blacklisted term from the markdown text or update the forbidden term lists in your local environment configuration.

See Also​