Catch issues earlier
Find UI5 problems while you are still working, before they reach review or production.
Local analysis for SAPUI5 and Fiori
Catch UI5 problems before production.
KAEV runs focused health, security, architecture, and performance checks directly inside your project. No source upload and no dashboard to configure.
Runs locallyLinux · macOS · Windows
No source uploadAvailable on npm ↗
Why KAEV?
A focused second pair of eyes for UI5 projects, without adding another platform to your workflow.
Keep your code local
KAEV runs inside your project. Your source code is not uploaded to a remote service.
Act on clear findings
See severity, confidence, rule IDs, and file locations directly in the terminal.
What KAEV checks
One command checks the areas most likely to turn into UI5 maintenance, security, or production problems.
UI5 & configuration
Validate project structure, manifests, UI5 configuration, stable IDs, localization, global Core access, and official linter findings.
Security
Detect exposed credentials, unsafe browser storage, dynamic execution, insecure transport, and missing protection boundaries.
Architecture
Review networking boundaries and patterns that work against UI5-managed rendering.
Performance & OData
Check synchronous requests, lifecycle cleanup, refresh placement, V2/V4 collection operations, and model size limits.
Built for your workflow
From terminal output to a shareable report.
Run checks in the current project, review actionable findings in place, then create a Markdown report when you need a durable record.
Current projectTerminal findingsMarkdown report
What's new
Broader analysis, safer across platforms.
KAEV now follows modern OData V4 flows, detects lifecycle cleanup and synchronous-request risks, checks XML localization, and normalizes Windows project paths. Node.js 22 and 24 are officially supported, with temporary Node.js 20.11+ compatibility.
Read the changelog ↗Quick start
Install KAEV
Run the checks
Review passes, findings, severity, confidence, and file locations in the terminal.
Create a report
Generate a Markdown report in the current project directory.
Ready when your project is