Skip to content
KAEV

Platforms

KAEV is tested on Windows, macOS, and Linux. The CLI commands and result schema are the same on every platform; internal finding paths always use / so baselines, suppressions, SARIF, and JSON remain portable.

Supported Node.js versions

Section titled “Supported Node.js versions”
Runtime Support
Node.js 22 (22.12.0+) Officially supported
Node.js 24 Officially supported
Node.js 20.11.0+ Temporary, deprecated enterprise compatibility
Node.js 18 and earlier Unsupported; KAEV exits with code 2
Untested odd/current majors Unsupported until explicitly added and verified

Use the latest patch release within a supported major. Confirm the runtime and KAEV installation with:

Terminal window
node --version
npm --version
npx @satiroglu/kaev@latest --version

Windows

Section titled “Windows”

PowerShell:

Terminal window
cd C:\work\my-ui5-app
npx @satiroglu/kaev@latest check
npx @satiroglu/kaev@latest doctor

Command Prompt uses the same commands. KAEV accepts native backslashes in configured UI5 source roots and normalizes reported locations to /. Drive-qualified, UNC, absolute, and traversal paths are rejected where configuration requires a project-relative path.

For redirected output, use the CLI format explicitly:

Terminal window
npx @satiroglu/kaev@latest check --format json | Out-File -Encoding utf8 kaev-result.json

Explicit UTF-8 output avoids the UTF-16 redirection behavior of older Windows PowerShell versions. In Command Prompt, ordinary > redirection is suitable.

If a global install is not found, prefer npx @satiroglu/kaev@latest or ensure npm’s global binary directory is present in PATH.

macOS

Section titled “macOS”

Terminal with zsh or bash:

Terminal window
cd ~/work/my-ui5-app
npx @satiroglu/kaev@latest check
npx @satiroglu/kaev@latest doctor

Use an actively maintained Node installation and avoid relying on an outdated system-provided runtime. Apple Silicon and Intel architecture are reported by kaev doctor; KAEV itself is JavaScript and does not require a platform-specific Kaev binary.

Linux

Section titled “Linux”

Bash and other POSIX-compatible shells:

Terminal window
cd /workspace/my-ui5-app
npx @satiroglu/kaev@latest check
npx @satiroglu/kaev@latest doctor

In containers and CI, pin a supported Node image and install KAEV as a development dependency for reproducibility. Ensure the project directory is readable. KAEV analysis is read-only unless you explicitly run report, init, or baseline.

Cross-platform behavior

Section titled “Cross-platform behavior”
  • Run KAEV from the individual UI5 project root unless using kaev workspace.
  • .kaevrc.json and baseline filenames must be direct files in the project root.
  • Symlinks are excluded during discovery; report parent directories may not be symlinks.
  • ANSI color is automatic only for interactive terminals. Use --color always, --color never, --no-color, or NO_COLOR when needed.
  • Machine-readable stdout is stable across platforms; operational and debug messages go to stderr.
  • UI5 Linter runs in a restricted child process using the Node permission flag appropriate to the active supported runtime.