Describe the bug
Following @esnible's report in rossoctl/cortex#533 that a URL inside a backtick/code section was flagged, we confirmed that current lychee excludes URLs inside inline code spans and fenced code blocks by default (verified in the scanner's runtime environment). So code-block URLs are already excluded today.
However, the setup docs (docs/running-without-openclaw.md) install lychee with an unpinned brew install lychee and there is no documented minimum version. lychee's verbatim/code-block handling is version-dependent (--include-verbatim opts URLs back in), so an upgrade or a differently-configured environment could reintroduce the code-block false positives.
Proposed fix
- Document a minimum lychee version whose default excludes verbatim (code-block) URLs, and pin it in the install step in
docs/running-without-openclaw.md.
- Optionally add a short note in the scanner/skill that the scanner relies on lychee's default code-block exclusion (i.e. must not pass
--include-verbatim).
Additional context
Describe the bug
Following @esnible's report in rossoctl/cortex#533 that a URL inside a backtick/code section was flagged, we confirmed that current lychee excludes URLs inside inline code spans and fenced code blocks by default (verified in the scanner's runtime environment). So code-block URLs are already excluded today.
However, the setup docs (
docs/running-without-openclaw.md) install lychee with an unpinnedbrew install lycheeand there is no documented minimum version. lychee's verbatim/code-block handling is version-dependent (--include-verbatimopts URLs back in), so an upgrade or a differently-configured environment could reintroduce the code-block false positives.Proposed fix
docs/running-without-openclaw.md.--include-verbatim).Additional context
.svcsuppression fix.