Everything in UI5
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Distributed through
Installs into
CDS plugin and UI5 controls for AI text features via SAP AI Core
It is text processing, not an agent: there is no tool calling, no retrieval and no conversation. It needs SAP AI Core, and the backend half needs [@sap-ai-sdk/orchestration](artifact:sap-ai-sdk-orchestration) installed alongside it — an optional peer, so a frontend-only install stays lean.
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
UI5 Tooling command line for project setup, dev server and build
VS Code extension to serve, proxy, build and deploy UI5 projects
UI5 Tooling module deploying Fiori/UI5 apps to SAP systems
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
Command line for changing features of an existing Fiori project
Rule-based checker for SAPUI5 and OpenUI5 projects
Not in a project whose dependencies must all carry an open-source licence: KAEV is proprietary software, its licence page states that downloading or viewing the npm package does not by itself grant permission to use, copy, modify, redistribute, sublicense, sell, host or create derivative works, and the LICENSE file shipped with the package carries the controlling terms. Not as the last word on whether a UI5 application is secure: its rule reference states that a heuristic finding is not proof of a vulnerability, and its documentation puts professional security review beside it rather than under it.
Static analysis tool for UI5 projects
SAPUI5 extension for Visual Studio Code
Its README assumes a `manifest.json` with an app ID, JavaScript files that start with `sap.ui.define`, and access to ui5.sap.com to preload the standard library metadata. It says of TypeScript that ts-morph, its parser there, has drawbacks, and that not all linters work for TypeScript.
Command-line linter for UI5 classes, XML views and i18n files
Two of its JavaScript and TypeScript checks, EventTypeLinter and WrongNamespaceLinter, apply to TypeScript projects only.
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
Command line running UI5 QUnit and OPA tests in parallel
VS Code extension generating OData mock data from service metadata
Rule-based checker for SAPUI5 and OpenUI5 projects
Not in a project whose dependencies must all carry an open-source licence: KAEV is proprietary software, its licence page states that downloading or viewing the npm package does not by itself grant permission to use, copy, modify, redistribute, sublicense, sell, host or create derivative works, and the LICENSE file shipped with the package carries the controlling terms. Not as the last word on whether a UI5 application is secure: its rule reference states that a heuristic finding is not proof of a vulnerability, and its documentation puts professional security review beside it rather than under it.
CLI translating UI5 i18n.properties files with OpenAI
CLI converting UI5 i18n properties files to Excel and back
Release and repository quiet for 39 months.
VS Code side bar view of the SAPUI5 and OpenUI5 API reference
Pro-code CLI for building and deploying Joule Studio solutions
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.