Everything in the atlas
Type
Domain: UI & Frontend Bridge
Origin
Signals: 2
Content
More
Group by: Capability
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.
UI5con 2026 workshop fixing accessibility defects in a UI5 app
SAP's Node.js application router in front of business applications
Approuter session held in a bound Redis cache instance
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
Fiori elements app in the HTML5 Application Repository with cdm.json
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
MTA deploying CAP, HDI container and a Fiori elements app
HTML5 apps on the HTML5 Application Repository across CF and Kyma
UI5 app deployed to Cloud Foundry via three approuter setups
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 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
Command line generator of UI5 custom controls from html
Release and repository quiet for 29 months.
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.
Template repository for own UI5 artefacts served to abap2UI5
Live icon browser for the ui5-fontawesome-lib icon set
Framework core: module loader, MVC runtime, binding, routing, theming
OpenUI5 JSONModel extension with CRUD over HTTP
OpenUI5 OData V2 model extension with Promises
SAPUI5 library generating OData V2 metadata-based dialogs and pages
Release and repository quiet for 26 months.
CAP and UI5 app for in-place table maintenance with SmartTable
Neither the package manifest nor the repository tree declares a licence.
UI5 app built with openui5-fhir against FHIR services
CAP plugin putting a draft-capable facade in front of imported OData
CAP Node.js runtime
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Convention-based handler layer for CAP with draft lifecycle hooks
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Event registration app showing OData V4 draft with UI5 and CAP
CAP plugin generating value help for enum fields from an annotation
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
OASIS and SAP OData vocabularies with a VocabularyService
CAP Node.js runtime
Entry point for generating a Fiori application from a template
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
User details and quickview links for createdBy and modifiedBy
Floorplans rendered from CDS UI annotations as abap2UI5 apps
Not the whole addon in ABAP Cloud: the DDIC annotation service is not released there, so the annotations come through XCO instead, a database table is read-only, the DDL source is not read, and the cloud path was written without a cloud system to run it on. Not for a plain internal table, since it renders from CDS annotations; the README points at `z2ui5_cl_ui5_view_builder` for that case. As of 2026-10 the maintainer states that none of it has been clicked through in an SAP system: the RAP write path and the reading of metadata extensions were written from documentation and pass the three offline gates only.
CDS vocabulary for User-Rendered Patterns display annotations
The declared repository is github.com/your-username/urp-vocab, an unedited placeholder. Three releases, September 2025.
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
Neither the package manifest nor the repository tree declares a licence.
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
Singleton entity whose flags drive Fiori elements feature control
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
Incident Management reference application for CAP
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
CAP and UI5 app for in-place table maintenance with SmartTable
Neither the package manifest nor the repository tree declares a licence.
Showcase of Fiori elements for OData V4 features on RAP
Travel-booking reference app on CAP Node.js and Java backends
Showcase of Fiori elements for OData V4 features on a CAP backend
CodeJam building a bookshop app on the flexible programming model
TechEd 2022 workshop mixing SAPUI5 with Fiori elements building blocks
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
Session building a travel dashboard with Fiori elements and SAPUI5
Fiori Innovation Day session building a travel dashboard
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
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.
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.
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
CAP bookshop showing UI5 development with cds-plugin-ui5