Everything in the atlas
Type
Domain
Origin: Not from SAP
Signals: 2
More: UI5
Group by: Capability
UI5 control library for file upload and download in front of CAP
UI5 component adding a spreadsheet upload dialog to Fiori apps
UI5 app template deploying the Spreadsheet Importer once to ABAP
Adaptation project adding spreadsheet upload to Manage Banks
Neither the package manifest nor the repository tree declares a licence.
UI5 app opening the Spreadsheet Importer on on-premise OData services
Agent skill generating a Joule Frontend Actions bridge for UI5 apps
Five MCP servers whose tools return a prebuilt UI
Neither the package manifest nor the repository tree declares a licence.
UI5 app reading the signed-in user via launchpad and approuter
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The repository publishes no licence, so reusing its code needs the author's permission.
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
VS Code extension to serve, proxy, build and deploy UI5 projects
UI5 Tooling module deploying Fiori/UI5 apps to SAP systems
UI5 CLI middleware proxying the dev server through @sap/approuter
UI5 CLI middleware running a CDS server inside the UI5 dev server
Experimental UI5 middleware for hot module replacement
UI5 middleware syncing interactions across browsers over websocket
UI5 middleware serving a chosen welcome page at the root path
Live reload middleware for the UI5 dev server
UI5 middleware recording OData traffic as mock server datasets
It records what the app actually asked for, so an entity no recorded journey touched is not in the dataset and replay will not answer for it. Its own README asks for `fiori-tools-appreload` to be disabled while recording, because a reload loop is what happens otherwise.
UI5 middleware logging in with Playwright and reusing the session
UI5 middleware serving a locally built UI5 framework
UI5 middleware serving static resources from a path or npm package
Dev-server middleware proxying requests to a backend system
UI5 middleware including one UI5 application in another
UI5 middleware serving static resources from JAR files (WebJars)
WebSocket support for Express-based dev servers such as UI5's
UI5 Tooling task writing the service name into the importer manifest
UI5 builder task cachebusting standalone UI5 applications
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
UI5 builder task appending copyright headers to source files
UI5 builder task generating d.ts type declarations
UI5 builder task flattening library output for SAP NetWeaver
UI5 builder task checking XML views for missing i18n texts
UI5 builder task minifying HTML, CSS and JSON files
UI5 builder task minifying XML views and fragments
UI5 builder task turning a UI5 app into a progressive web app
Build task packaging the UI5 build result as a zip archive
UI5 CLI extension compiling Less files into CSS
UI5 tooling extensions loading npm packages as UI5 modules
UI5 CLI extension for string replacement during the build
UI5 CLI extension transpiling code during the UI5 build
UI5 app carrying 18 UI5 CLI extensions in one configuration
UI5 app consuming the cds-bookshop server via ui5-middleware-cap
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
Sample setup for developing a UI5 library
Custom UI5 control packaged as an npm package
pnpm workspace developing a UI5 app, library and plugin together
Neither the package manifest nor the repository tree declares a licence.
TypeScript UI5 app consuming custom UI5 CLI extensions together
TypeScript UI5 app consuming @ui5/webcomponents
TypeScript UI5 module consumed through ui5-tooling-modules
npm-init wrapper for the Easy-UI5 Yeoman generator
Yeoman meta-generator for scaffolding UI5 projects
Easy-UI5 generator scaffolding a new UI5 application
Easy-UI5 generator scaffolding a new UI5 library
Yeoman generator for UI5 projects holding several applications
Not for a single-application project with no deployment configuration: for that the README points to [generator-ui5-app](artifact:ui5-community-generator-ui5-app) instead.
Easy-UI5 generator scaffolding a TypeScript UI5 application
Generator for a TypeScript UI5 FlexibleColumnLayout app on OData
Easy-UI5 generator scaffolding a TypeScript UI5 library
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.
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.
Plugin-based JSX runtime for UI5 views written as .tsx
Lowercase HTML tags such as `<div>` typecheck but throw: the default renderer constructs UI5 controls, and the HTML-aware renderer plugin is described as planned. `withScope` restores the previous scope on a synchronous return only, so an `await` inside its callback leaks the scope on runtimes without `AsyncLocalStorage`. A view that has to stay adaptable through UI5 flexibility has no path here yet: the project's [Devtoberfest session](content:devtoberfest-2026-ui5-views-type-safe-tsx) states that flexibility support is not built in yet.
Babel transformer from modern ES or TypeScript to UI5 module syntax
UI5 builder task generating d.ts type declarations
UI5 Tooling task transpiling TypeScript and ES modules
pnpm workspace developing a UI5 app, library and plugin together
Neither the package manifest nor the repository tree declares a licence.
TypeScript UI5 app consuming custom UI5 CLI extensions together
TypeScript UI5 app consuming @ui5/webcomponents
TypeScript UI5 library with build, linting and Karma tests
TypeScript UI5 module consumed through ui5-tooling-modules
Karma preprocessor transpiling UI5 sources via ui5-tooling-transpile
UI5 middleware recording OData traffic as mock server datasets
It records what the app actually asked for, so an entity no recorded journey touched is not in the dataset and replay will not answer for it. Its own README asks for `fiori-tools-appreload` to be disabled while recording, because a reload loop is what happens otherwise.
Command line running UI5 QUnit and OPA tests in parallel
Vitest environment running UI5 unit tests in Node.js
VS Code extension generating OData mock data from service metadata
WebdriverIO service running QUnit test pages
End-to-end testing for UI5 on WebdriverIO with UI5 control selectors
Where the login cannot be completed by configuration. Its authentication page states that multi-factor authentication is not supported, because a media break between browser and phone cannot be managed out of the box.
UI5 app carrying 18 UI5 CLI extensions in one configuration
Ten exercises on the Fiori elements mock server middleware
Neither the package manifest nor the repository tree declares a licence.
Sample setup for developing a UI5 library
TypeScript UI5 app consuming custom UI5 CLI extensions together
TypeScript UI5 library with build, linting and Karma tests
UI5 library of eight composite controls under the ui5x namespace
The README states that UI5X is in early development and that APIs may change before version 1.0. Styling covers the `sap_horizon` and `sap_fiori_3` families with their dark and high-contrast variants; any other theme falls back to the base theme.
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
UI5 custom control wrapping Chart.js for line charts
UI5 library adding Font Awesome icon sets to sap-icon://
UI5 library of eight composite controls under the ui5x namespace
The README states that UI5X is in early development and that APIs may change before version 1.0. Styling covers the `sap_horizon` and `sap_fiori_3` families with their dark and high-contrast variants; any other theme falls back to the base theme.
Live icon browser for the ui5-fontawesome-lib icon set
OpenUI5 JSONModel extension with CRUD over HTTP
OpenUI5 library validating view fields against JSON schema
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.
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
CLI translating UI5 i18n.properties files with OpenAI
UI5 control library of sized sap.m controls and touch inputs
Custom UI5 Web Components bundle loaded with one script tag
TypeScript UI5 app consuming @ui5/webcomponents
Hosted app listing changes between SAPUI5 or OpenUI5 versions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It reports what the change log says, not what your application uses, so it cannot tell you which of the listed changes touches your code. The repository carries no licence file, which leaves the code itself with no grant attached even though the hosted app is open to use.
VS Code side bar view of the SAPUI5 and OpenUI5 API reference
Scaffolded UI5 TypeScript app consuming the JSX runtime
It shows the wiring and a converted view pair, not the runtime's API surface; the directives, the plugin SPI and the binding forms are demonstrated in [@ui5-community/jsx-runtime-showcase](artifact:ui5-community-jsx-runtime-showcase) instead.
Showcase and documentation app of @ui5-community/jsx-runtime
Its views are not a template for application code: every showcase view overrides `getController()` to return itself so a sample stays readable in one file, and the gotchas page says not to ship that in production, where a view keeps a separate `*.controller.ts`. Routing from a sample, an `ODataModel` v2 or v4, `sap.ui.mdc.Table`, forms and custom control authoring in TSX are absent by decision and documented as deferred.