Kendo UI Core: the free subset of a commercial widget suite, and the divide it draws

The README is a feature matrix, not documentation

There is no install command, no quick start and no API example in this README. What it contains instead is a three-column table: Kendo UI Core, Kendo UI Professional, and UI for ASP.NET MVC and ASP.NET Core. Every row is a widget, and each cell is either a check mark or a cross. Reading it left to right tells you which widgets the free build ships.

The divide lands in awkward places. Under data management, ListView and Pager are in Core, while Grid, FileManager, Spreadsheet, PivotGrid, TreeList and Filter are not. Under editors, most of the familiar ones are free: AutoComplete, Color Picker, ComboBox, DateInput, DatePicker, DateTimePicker, DropDownList, ListBox, MaskedTextBox, MultiSelect, NumericTextBox, Slider, TextBox, TimePicker and Validator. The rich text Editor, Upload, Rating, Switch, DateRangePicker, DropDownTree and MultiColumnComboBox are not.

The consequence is that the single most recognisable Kendo widget, the Grid, is not part of Kendo UI Core. A team that wants Telerik's look and its form controls can get them free. A team that wants a data grid is on a commercial licence from the start, and no amount of reading the README changes that.

What the package metadata says about the build

The repository tree is more informative than the README. `src/` holds the widget sources, `typescript/` the type definitions, `docs/` and `docs-aspnet/` the documentation, `tests/` the test suite, `build/` the build scripts, and `resources/` shared assets. Two build entry points sit at the root, which is the first sign of a migration in progress.

`package.json` is where the real details live:

{
  "name": "kendo-ui-core",
  "main": "js/kendo.ui.core.js",
  "author": "Telerik",
  "license": "Apache-2.0",

Two things stand out. The published version field is `1.0.0` and has clearly not tracked the release tags, which are calendar-versioned and currently sit at 2026.3.811. And the `main` entry points at a built path, `js/kendo.ui.core.js`, so what you get from a registry is an assembled bundle rather than the ES modules in `src/`.

The license field is worth pausing on, because it disagrees with the repository metadata. GitHub reports the repository license as NOASSERTION, while `package.json` declares Apache-2.0 and a `LICENSE.md` file is present in the tree. All three can be true at once if the file carries extra terms, which is common for a commercially supported product. If the license matters to you, read `LICENSE.md` rather than trusting either the metadata field or the short string in `package.json`.

A build system carrying two toolchains at once

The root of the repository has `gulpfile.js` and a `gulp` dependency at version 4, alongside `rolldown.config.mjs` and `rolldown.config.dev.mjs`. The dev dependency list also carries `@rollup/plugin-node-resolve`, `@rollup/plugin-typescript`, `@rollup/plugin-virtual` and `@rollup/stream`, plus a full set of gulp plugins for filtering, streaming, sourcemaps and terser.

Both toolchains are present, which tells you a bundler migration is underway rather than finished. Rolldown is the newer addition, and the rollup plugins are still declared alongside it, most likely because the gulp pipeline still drives the legacy tasks. For a project that publishes a single bundled file with its own plugin system, that is a plausible interim state and not a red flag. It does mean the build is not obviously reproducible from the README, since it does not document either entry point.

The rest of the dev dependencies describe the test setup clearly enough. There is Vitest at 4.1.11, Playwright at 1.63.0, `@vitest/browser-playwright` for running browser tests, `axe-core` for accessibility assertions, and `@progress/wct-a11y-spec` for accessibility specifications. A widget library whose test stack includes an accessibility conformance suite is making a differentiator claim, and this is the concrete evidence behind it.

Theming versions and the release train

Kendo UI is released three times a year under calendar-versioned tags. The three most recent releases are 2026.3.811 published on 2026-08-12, 2026.2.520 on 2026-05-20, and 2026.1.415 on 2026-04-15. The last push to the repository was on 2026-09-24, and with 682 open issues the project is actively worked rather than merely maintained.

Each release body is short and lists supported theme package versions rather than changelog entries. That is a clue about where the real work sits: theming is versioned separately from the widget code, so the themes move in lockstep with the release train.

The theme list itself changed between releases. 2026.3.811 and 2026.2.520 both list six themes: bootstrap, classic, default, fluent, material and meridian, all at 14.5.0 and 14.1.0 respectively. The earlier 2026.1.415 lists only five, omitting meridian, with its packages at 13.1.1. So meridian arrived with the 2026.2 release, which is the kind of detail you only get from reading the release bodies side by side.

Because every theme and the widget code share a version number, upgrading is a coordinated operation: bumping the theme packages without the core package, or the reverse, is the kind of mismatch the versioned scheme exists to prevent.

jQuery is still a declared dependency

The repository description calls Kendo UI Core an HTML5, jQuery-based widget library, and `package.json` still declares `jquery` in devDependencies at version 4. That version number is the interesting part. jQuery 4 is a major release, and pairing the widget layer with it is a deliberate compatibility choice rather than an inherited default.

Whether jQuery is a runtime peer dependency or only a build-time test fixture cannot be settled from the manifest alone, since the `peerDependencies` block was not part of what the repository page shows. The honest reading is that the jQuery relationship is real and maintained, but the exact boundary between runtime requirement and development aid is a question for the package manifest you actually install.

For a team starting a new project, this is the part of Kendo UI that deserves the most scrutiny. The editors and the Grid are both jQuery-era technology, and the alternative now is usually a framework-native component set. Kendo UI answers that objection with wrappers for React, Angular, Vue and others, which is what the `docs/` and `docs-aspnet/` trees support, but each wrapper is a separate distribution and a separate version line from the jQuery core.

Editorial conclusion

Kendo UI Core is worth choosing when you want Telerik's editors, theming layer and accessibility testing with the Grid and charts removed from the equation, because the divide is drawn at widget level rather than by crippling the free tier. It is a poor fit the moment your application needs a data grid, since that widget sits squarely in the commercial column and the free build offers only ListView and Pager in the same category. Read the feature matrix before you install anything, then read the package.json to see that the published artifact is still versioned 1.0.0 with a hand-written main entry while releases ship under calendar-versioned tags.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. telerik/kendo-ui-core on GitHub