openui5 ships three release lines, and npm test only runs lint
OpenUI5 lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice.
At a glance
- What is it?
- The open source UI5 runtime, distributed as a download or through a separate CLI rather than from npm. The repository carries three release lines at once, three build systems, four license artefacts, and a script named test that runs eslint instead of the test suite.
- Who is it for?
- openui5 fits an enterprise team that wants the SAPUI5 control set under an Apache 2.0 licence and is prepared to consume it as a versioned runtime download rather than a registry dependency. It does not fit a team that wants `npm install openui5`, because that package is marked private, and it does not fit anyone who needs one support line, because three minors were shipping in the same week.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- UI5/openui53,325 ★ · +8
| Repository | 2026-09-24 | 2026-11-21 |
|---|---|---|
| UI5/openui5 | 3.3k | 3.3k |
8 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
npm test runs eslint, and the suites live behind karma
The manifest has a script named `test` and it does not run tests. It is defined as `npm run lint`, and `lint` in turn is `eslint ./src --quiet --cache`. So the command anyone reaches for first verifies style and stops there. The actual test suites are a separate family of scripts built on karma. One entry, `karma`, runs `karma start lib/test/karma.conf.js`, and there is one script per control library: `karma:sap.f`, `karma:sap.m`, `karma:sap.tnt`, `karma:sap.ui.codeeditor`, `karma:sap.ui.commons`, `karma:sap.ui.core`, `karma:sap.ui.documentation`, `karma:sap.ui.dt`, `karma:sap.ui.fl` and `karma:sap.ui.mdc`, each passing a `--lib=` argument. Three aggregators sit on top, `karma-all` running them with npm-run-all, plus coverage and CI coverage variants. Style has its own separate command too, `lint:styles`, which runs stylelint over the Less sources. Two consequences for anyone wiring this into CI: the cheap command proves nothing about behaviour, and the expensive one has to enumerate libraries.
Three release lines, and the snapshot sits a minor ahead
OpenUI5 does not run one version line. Three recent releases are 1.153.0 on 2026-09-29, 1.148.9 on 2026-09-23 and 1.136.21, also on 2026-09-23. Two different minors shipped on the same day, and the third landed six days later. That pattern says these are parallel maintenance lines rather than one line with backported patches, which is the normal shape for a runtime that enterprises pin for years: you stay on a minor, and it keeps receiving fixes. It also means the highest number is not the only thing receiving attention. The root manifest sits one minor beyond the newest tag, at version `1.154.0-SNAPSHOT`, so what you read in the repository is the in-development line and not what you would download. Version management is a Maven concern here rather than an npm one, which the tree reflects: there is a `pom.xml` at the root and a `.version-tool.xml` configuring the version tooling, alongside the npm manifest. A Renovate configuration is present as well, so dependency updates are automated even though the version number is not.
The root package is private, so npm is not an install path
`npm install openui5` is not how this runtime reaches an application, and the manifest says why. The root package is named `openui5`, described as OpenUI5 Core & Runtime, and marked `private: true`, which means it is never published to the registry. The two documented routes are elsewhere. The first is a download page at openui5.org/releases, which offers the complete UI5 runtime on its own, or the UI5 SDK, which bundles the documentation, a set of example applications and the complete runtime as well. So the choice is between a runtime-only artefact and a much larger one that includes docs and samples, and the difference in payload is the first decision to make. The second route is UI5 CLI, hosted at its own site under the ui5 GitHub organisation and named the recommended tool for working with OpenUI5, with the stated jobs of managing framework dependencies and building optimized packages for applications, components and libraries. Note that this is a separate project: nothing in this repository builds the runtime for a consumer, it builds the runtime for itself.
Four licence artefacts, and the third-party one is the one to read
Licensing is handled with more care here than in most framework repositories, and it takes four files to do it. The project's own terms are Apache License 2.0 in `LICENSE.txt`. Third-party open source modules bundled into the runtime are listed with their respective licences in `THIRDPARTY.txt`. The same third-party licence information is also published in machine-readable form in `REUSE.toml`, which is the file a compliance tool consumes rather than a human. And the tree carries a `LICENSES/` directory, which is where the REUSE specification keeps per-file licence texts. The README is explicit that the runtime contains third-party modules in addition to the Apache grant, so treating `LICENSE.txt` as the whole answer is a mistake: a bundled control library can carry terms of its own. If your organisation runs a licence scan, point it at `THIRDPARTY.txt` and `REUSE.toml` and let the machine-readable file do the work rather than reading the prose list.
Support questions get filed under the sapui5 tag
The README routes you to four places for help, and three of them belong to SAP rather than to this project. There is a SAP Community Forum thread, described as carrying 20,000 or more questions and answers, there is SAP Business Application Studio for the app templates, and the Stack Overflow tag to use is `sapui5`, not `openui5`. The fourth is the project's own Slack. The practical effect is that the searchable public record for this runtime lives under SAP's product name. A developer who searches for `openui5` on Stack Overflow finds less than one who searches `sapui5`, and a question filed under the wrong tag is effectively invisible to the people who could answer it. The app templates have the same split: they are available inside SAP Business Application Studio or from SAP's GitHub organisation rather than from this repository. For an open source project whose whole argument is independence from a vendor, the support funnel is the part of the arrangement most worth raising with your team before you commit.
Grunt, npm workspaces and Maven all build the same tree
Three build systems coexist in one repository. A `Gruntfile.js` and a `grunt/` directory carry the older pipeline, and one script, `start-grunt`, still invokes `grunt serve` directly. The npm side is workspace-based: the top-level scripts for starting, for the test suite, and for building or serving the SDK all delegate with `--workspace src/testsuite`, which means the actual implementation of those tasks lives in that workspace rather than at the root. Link management has its own pair, `link-all` and `unlink-all`, both delegating to `wsrun --serial`. The Maven side exists for versioning, through `pom.xml` and `.version-tool.xml`. Two other configuration files point away from JavaScript entirely: `.repo` is a manifest for Android's repo tool, and `.xmake.cfg` configures xmake, a native build system, which suggests at least one component of the tree is not pure JavaScript. Editor and style configuration is also split across generations, with `.eslintrc.json` alongside `.stylelintrc.mjs` and `.editorconfig`, and the Less sources styled separately from the JavaScript.
Data binding covers three models, and the browser claim has no number
The functional description is short and specific. OpenUI5 is a client-side HTML5 rendering library with a rich set of controls, based on JavaScript and following web standards, which supports data binding to different data models: JSON, XML and OData. Three binding targets is the concrete part of that sentence and the part that decides whether the library fits, since OData in particular is a SAP convention and the cost of that binding is a dependency on a specific service shape. The rest of the positioning is not falsifiable. The README says enterprise-ready, responsive to all devices, and running on almost any browser of your choice, and it attaches no browser matrix, no device list and no version numbers to any of the three. For a runtime you are pinning for years, that gap matters more than usual: the controls are the substance, and the browser support statement is the thing you would want pinned down before a procurement conversation. There is a control playground and a set of sample applications on the SDK site if you want to see the actual surface rather than the description of it.
Editorial conclusion
openui5 fits an enterprise team that wants the SAPUI5 control set under an Apache 2.0 licence and is prepared to consume it as a versioned runtime download rather than a registry dependency. It does not fit a team that wants `npm install openui5`, because that package is marked private, and it does not fit anyone who needs one support line, because three minors were shipping in the same week. Before adopting, pick a release line and note which of the three you are on, read THIRDPARTY.txt and REUSE.toml alongside LICENSE.txt rather than assuming the runtime is a single artefact, and remember that `npm test` in this repository lints rather than runs the karma suites.
Frequently asked questions
ui5 and openui5
OpenUI5 is the runtime published from this repository, whose root package is named openui5 and described as OpenUI5 Core & Runtime. That package is marked private, so it is not installed from the npm registry; the runtime comes from the download page or through the separate UI5 CLI. The community links in the README point at SAP forums and at the sapui5 tag on Stack Overflow.
openui5 vs react
The README does not compare OpenUI5 with React and links to no benchmark. What it does state is that OpenUI5 is a client-side HTML5 rendering library with a rich set of controls, based on JavaScript, following web standards, and supporting data binding to JSON, XML and OData.
openui5 alternatives
No alternatives are named. The paths the README does offer are the release download page, for either the complete runtime or the larger UI5 SDK with documentation and example apps, and the UI5 CLI, which it calls the recommended tool for managing framework dependencies and building optimized packages.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ui5-openui5)Star history chart for your README
[](https://hysenlabs.com/projects/ui5-openui5)Was this useful?