Library / SDK
highcharts/highcharts avatar
highcharts/highcharts

Highcharts JS: what the working repo actually gives you

Highcharts JS, the JavaScript charting framework

12,502 stars3,863 forksTypeScriptNOASSERTION

At a glance

What is it?
Highcharts is a source-available JavaScript charting library built on SVG with canvas and WebGL extensions. The npm package is the practical entry point; this repository is the build tree behind it, and its licence is not an open source one.
Who is it for?
Adopt Highcharts when you need a broad chart type catalogue, SVG output that prints and exports cleanly, and you are prepared to work through the licensing terms on shop.highcharts.com. Do not adopt it if an OSI-approved licence is a hard requirement for your procurement or distribution model, because the repository describes itself as source available, not open source.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • highcharts/highcharts12,502 ★ · +11
Star history
Repository2026-09-222026-11-15
highcharts/highcharts12.5k12.5k

11 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Who Highcharts is built for, and who it is not

Highcharts targets teams that need a wide catalogue of chart types in a browser and are willing to pay for it. The readme frames the product as "source available" and sends licensing questions to shop.highcharts.com, which is the single most important sentence in the file. If your organisation treats OSI-approved licensing as a procurement gate, this repository fails that gate by design. The licence field on the repository is NOASSERTION, meaning no standard identifier was applied.

The repository itself is not the artefact most users want. It is the working tree for Highcharts code, and the readme says so directly: if you simply want to include Highcharts in a project, use the distribution package on npm or the download page. That distinction matters because the build tree carries Gulp tasks, Cypress and Playwright configs, sample directories for highcharts, stock, maps, gantt, dashboards, grid-lite and grid-pro, and a large test tree. Cloning it to draw a line chart is the wrong move.

It is also not a lightweight option. SVG rendering produces a DOM node per element, which is the right trade for accessibility and crisp export but the wrong one for a scatter plot with hundreds of thousands of points. The readme mentions canvas and WebGL, so heavier series exist, but the default mental model is SVG.

How Highcharts renders: SVG first, canvas and WebGL where needed

The readme describes Highcharts as a JavaScript charting library based on SVG and some canvas/WebGL. That single line explains most of the behaviour you will observe. Charts are constructed as SVG documents, so every series, axis tick and label is a real element in the page. Screen readers can reach that structure, CSS can style parts of it, and the built-in export path has vector output to work with.

The cost is node count. A chart with many points creates many elements, and layout work scales with them. The canvas and WebGL paths exist for cases where SVG stops being reasonable, and the repository layout reflects how far that goes: there are separate sample and TypeScript config sets for highcharts, stock, maps and gantt, and separate product build scripts in package.json for Dashboards and Grid. Highcharts is not one bundle but a family, and each product has its own build, lint and test scripts.

Module loading is deliberately granular. The readme links to a page on creating custom Highcharts files, and gives the reason: reducing file size, or combining modules into one file to reduce latency. So the intended production shape is a custom build containing only the series and features you use, not the full bundle pulled from a CDN.

Installing Highcharts from npm and drawing a first chart

The readme gives the npm command directly. Run it in your project root; it writes highcharts into your dependencies. The package.json in the repository sets module to esm/highcharts.js, so bundlers that read the module field will pick up the ES module build.

bash
npm install --save highcharts

The alternative the readme offers is the CDN, which needs no install step at all. It gives this exact script tag, and the file it points at is the full highcharts bundle. Load it before your own script.

html
<script src="https://code.highcharts.com/highcharts.js"></script>

After either route, the chart itself is created by calling the library against a container element. The readme does not print a chart example inline; it points at the installation docs and the samples directory for that. The samples tree is the honest reference here, with separate folders for highcharts, stock, maps, gantt, dashboards, grid-lite and grid-pro, plus a demo-config.js and a template-example.htm. If you want to see working configurations rather than read prose, those sample files are the ground truth in this repository.

One setup detail worth knowing before you start: the readme warns that running Node natively on ARM64 macOS can break packages that compile natively, and names node-canvas specifically. The fix it gives is Homebrew plus a single install of the system libraries.

bash
brew install pkg-config cairo pango libpng jpeg giflib librsvg pixman

Building Highcharts itself, and why most readers should not

If you intend to modify the library rather than consume it, the readme describes the loop. Highcharts uses Gulp as its build system. After npm install in the root folder you run gulp, which sets up a watch task over the JavaScript and CSS files. Edits under /js or /css produce rebuilt files in the code folder. Other tasks exist, and the readme names gulp lint as one.

bash
npm install
gulp

API documentation is generated separately. The readme gives one command for it, npx gulp jsdoc-watch, which also starts a server serving the generated docs.

bash
npx gulp jsdoc-watch

Be realistic about the scope. The repository carries a changelog directory, a docs directory, an errors directory, i18n files, gfx assets, utils, tools, and test trees under both test/ and tests/. The package.json test script runs Playwright across setup projects for highcharts, dashboards, grid-lite, grid-pro and grid-shared, plus qunit, and there are separate dtest, gtest and test-node scripts for other products. That is a large surface to keep green if you fork. The readme also points contributors at CONTRIBUTING.md and repo-guidelines.md, which is where the actual rules live.

The licence is the real adoption decision

The readme does not describe licence tiers. It states that Highcharts is a source available product and refers readers to shop.highcharts.com for details. The repository's licence field is NOASSERTION and the top level contains a license.txt. That is the whole of what this repository supports.

What that means in practice: you cannot determine your obligations from the repository alone. Source available is not the same as open source, and the readme uses the term deliberately. Any evaluation that treats this repository like an MIT or Apache project is reading it wrong. The commercial terms, the free-use conditions and the support arrangements all sit behind the shop URL.

This also affects upgrade cost. Because the library ships as both a CDN bundle and an npm package, and because custom builds are a documented workflow, you have three moving parts to track: the package version, the CDN URL you pinned, and the module set in your custom build. Nothing in the readme describes a validation step for a custom build that omits a module you need.

Highcharts against Plotly.js, and the framework wrappers

Plotly.js is the comparison people search for most often, and the difference is architectural rather than cosmetic. Plotly.js is open source under MIT, which removes the procurement question entirely. Highcharts is source available with commercial terms set by the vendor. If your blocker is legal rather than technical, that single difference decides it and the rest of this section is moot.

If the blocker is technical, the split runs along rendering and scope. Highcharts builds SVG charts and adds canvas and WebGL for heavy series; the export and print story follows from the vector base. Plotly.js grew out of scientific plotting and carries a different default set of chart types and interactions. Neither is a drop-in for the other, and the readme gives no migration path.

Framework integration is the second thing to check carefully. The readme mentions a native iOS wrapper, highcharts/highcharts-ios, and states plainly that it is currently community-maintained. That word matters. A community-maintained wrapper means the release cadence is not the core team's, and you should confirm who is answering issues before you build a product on it. The readme says nothing about the status of React or Angular integrations, so check the installation docs before relying on one.

Maintenance, releases and what to verify before you commit

The repository is not archived. The last push was on 2026-11-02. That is the only maintenance signal available here. The repository has no published GitHub releases, so there is nothing to say about version cadence beyond the version string in package.json, which reads 13.1.1.

That package.json is marked private and its name is highcharts, which is worth pausing on. The working repo and the published npm package share a name but are not the same thing; the readme makes the split explicit by directing users to the distribution package on npm. If you file an issue or open a pull request, you are operating in the working repo, and CONTRIBUTING.md plus repo-guidelines.md govern that.

What to verify first, concretely. Open shop.highcharts.com and confirm which tier covers your deployment, because the readme offers nothing beyond that pointer. Decide whether you are consuming the npm package, the CDN bundle, or a custom build, and if it is a custom build, write down the module list, since the readme documents no way to detect a missing module before runtime. And if you are on iOS, confirm the maintenance status of highcharts/highcharts-ios yourself rather than assuming it tracks the core releases.

Editorial conclusion

Adopt Highcharts when you need a broad chart type catalogue, SVG output that prints and exports cleanly, and you are prepared to work through the licensing terms on shop.highcharts.com. Do not adopt it if an OSI-approved licence is a hard requirement for your procurement or distribution model, because the repository describes itself as source available, not open source. Before committing, verify two things: the exact licence tier that covers your deployment, and whether the wrapper for your framework is the official one or a community package, since the readme points iOS users at a community-maintained wrapper.

Frequently asked questions

Is Highcharts free or paid?

The readme describes Highcharts as a source available product and refers all licensing details to shop.highcharts.com. It does not state which uses are free and which require payment, so the shop page is the only place to confirm your case.

How do I install Highcharts?

The readme gives two routes: npm install --save highcharts, or a script tag pointing at https://code.highcharts.com/highcharts.js for the CDN. It notes that the repository itself is the working tree and that most users should use the distribution package on npm instead.

What is Highcharts used for?

It is a JavaScript charting library based on SVG with some canvas and WebGL, used to render charts in browser pages. The repository also carries samples and build scripts for related products including Stock, Maps, Gantt, Dashboards and Grid.

Which is better, Plotly.js or Highcharts?

The readme does not compare them. The one difference it does support is licensing: the readme calls Highcharts source available with terms at shop.highcharts.com, while Plotly.js is not described in this repository at all.

Can I use Highcharts in React?

The readme says nothing about React. It documents npm, the CDN, and ES6 modules, AMD and CommonJS via the installation docs, and it mentions a community-maintained iOS wrapper. For React, check the installation docs rather than assuming a wrapper exists.

Official sources

  1. highcharts/highcharts on GitHub
  2. Issues
  3. Project website
  4. README
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/highcharts-highcharts.svg)](https://hysenlabs.com/projects/highcharts-highcharts)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/highcharts-highcharts.svg)](https://hysenlabs.com/projects/highcharts-highcharts)

Was this useful?