Everything in UI5
Type: 4
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
UI5 control library for file upload and download in front of CAP
UI5 component adding a spreadsheet upload dialog to Fiori apps
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
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.
Framework core: module loader, MVC runtime, binding, routing, theming
UI5 library collecting an app's JavaScript errors
Release and repository quiet for 43 months.
Release and repository quiet for 37 months.
Internal logger of the UI5 CLI
UI5 CLI middleware for Istanbul code coverage
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
The declared repository is archived.
UI5 CLI middleware proxying the dev server through @sap/approuter
UI5 CLI middleware running a CDS server inside the UI5 dev server
UI5 Tooling middleware proxying destinations and neo-app.json routes
Quiet Release and repository quiet for 75 months.
Functional boundary It supports Basic Authentication only, so a backend that needs another method is not reachable through it.
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 dev server middleware adding an OpenID Connect login
UI5 middleware logging in with Playwright and reusing the session
UI5 server middleware proxying route prefixes to a backend
Release and repository quiet for 36 months.
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 v4 extension that registers other extensions
UI5 Tooling task writing the service name into the importer manifest
UI5 builder task cachebusting standalone UI5 applications
UI5 builder task preparing build output for the cachebuster
Release and repository quiet for 66 months.
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
UI5 builder task transpiling ES6 to ES5 with Babel
Release and repository quiet for 50 months.
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
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Writer of flexible programming model elements into Fiori elements apps
Writer that adds an OData service to an existing UI5 project
Writer of the base structure of a UI5 project from Node code
Framework core: module loader, MVC runtime, binding, routing, theming
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.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
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
Framework core: module loader, MVC runtime, binding, routing, theming
UI5 CLI middleware for Istanbul code coverage
Jest environment running UI5 unit tests in Node.js
Karma preprocessor transpiling UI5 sources via ui5-tooling-transpile
UI5 MockServer extension generating mock data with Faker.js
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.
Vitest environment running UI5 unit tests in Node.js
wdi5 plugin for Cucumber-style BDD tests on Fiori Elements apps
Archived The declared repository is archived.
No license Neither the package manifest nor the repository tree declares a licence.
wdi5 selectors for locating controls in Fiori Elements apps
Archived The declared repository is archived.
No license Neither the package manifest nor the repository tree declares a licence.
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.
Framework core: module loader, MVC runtime, binding, routing, theming
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 formatting dates with Day.js
No published releases; repository quiet for 52 months.
Thirteen custom UI5 controls for abap2UI5 apps
Needs Standard ABAP 7.50 or higher, and an abap2UI5 whose frontend reserves the resourceRoot `z2ui5_cci`: a frontend predating that rename reserves `z2ui5ccc` and cannot resolve the controls. Frontend artefacts only one company needs, such as an in-house reuse library, a corporate icon font or company CSS, are what [abap2UI5-addons/custom-controls-customer](https://github.com/abap2UI5-addons/custom-controls-customer) is for, the same mechanism under the second reserved root `z2ui5_ccc`. ExportSpreadsheet needs SAPUI5: under OpenUI5 `sap.ui.export` is missing and the button renders disabled.
UI5 control for live camera preview and PNG capture
Release and repository quiet for 28 months.
Release and repository quiet for 50 months.
OpenUI5 password input with strength scoring and rules
OpenUI5 control library for guided app tours
UI5 custom control wrapping Chart.js for line charts
UI5 custom control rendering Markdown to HTML
Release and repository quiet for 38 months.
UI5 custom control rendering a PDF from a base64 data URI
Quiet Release and repository quiet for 41 months.
Functional boundary The case it is written for is a document that has not been uploaded; anything already served from a URL is what the framework's own PDF control takes. Passing a document as a data URI means holding it in the page as a string first, which is a different cost from streaming it from a server.
UI5 control library with a button that delays enabling or showing
UI5 library adding Font Awesome icon sets to sap-icon://
UI5 control library wrapping C3.js charts as ui5.viz controls
On the second installation path there is no dependency to upgrade: the README states that for option b) all manual steps must be repeated every time the library version is updated.
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.
Framework core: module loader, MVC runtime, binding, routing, theming
OpenUI5 JSONModel extension with CRUD over HTTP
OpenUI5 OData V2 model extension with Promises
OpenUI5 library validating view fields against JSON schema
SAPUI5 library generating OData V2 metadata-based dialogs and pages
Release and repository quiet for 26 months.
OASIS and SAP OData vocabularies with a VocabularyService
Framework core: module loader, MVC runtime, binding, routing, theming
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
Reader and writer for i18n bundles of UI5 or CAP projects
Framework core: module loader, MVC runtime, binding, routing, theming
Framework core: module loader, MVC runtime, binding, routing, theming
Colour, font and metric definitions of the SAP themes
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
UI5 control library of sized sap.m controls and touch inputs
Framework core: module loader, MVC runtime, binding, routing, theming
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
The declared repository is archived.
SAP's UI elements as standard custom elements
Not where the UI library itself is expected to bind data: the documentation leaves binding a component's content and events to the host framework. Not from a CDN script tag: the project publishes none, so it assumes a build step.
abap2UI5 frontend rendering with UI5 Web Components
Not for views built from controls outside the portable profile: sap.ui.table, sap.f, sap.uxap, sap.ui.comp and z2ui5.cc custom controls render as a visible unsupported-control box and are listed in the diagnostics, and `CONTROL_BY_ID` and `BINDING_CALL` stay unsupported. Nine frontend actions the profile allows, `DOWNLOAD_B64_FILE` and `SYSTEM_LOGOUT` among them, are skipped and reported rather than run, and formatters other than the profile's `Formatter.Date*` render a placeholder.
Custom UI5 Web Components bundle loaded with one script tag
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Release and repository quiet for 36 months.
npm library parsing SAPUI5 and project UI5 class metadata
A project nested inside another is not parsed: its README says nested projects are not supported any more. A library installed from npm is read only when it ships its `-dbg.js` files and `manifest.json`.