Open-source project
plouc/nivo avatar
plouc/nivo

nivo breaks React charts into scoped packages you have to assemble yourself

nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries

14,141 stars1,074 forksTypeScriptMIT

At a glance

What is it?
nivo is a TypeScript monorepo of d3-based React chart components installed as one scoped package per chart type, with a separately deployed HTTP API for server side rendering. The README is short and leaves the package map, the renderer split and the release gap for you to work out.
Who is it for?
Adopt nivo if your team already works in React and can accept one scoped package per chart family and a per-component choice between SVG, HTML and Canvas. Read the Components Explorer before you commit, because the README will not tell you which package holds which chart, whether the version on npm has the prop you just read about, or how to silence the react-spring transitions.
Can I use it commercially?
Yes. MIT 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 117 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

  • plouc/nivo14,141 ★ · +40
Star history
Repository2026-09-222026-11-15
plouc/nivo14.1k14.1k

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

Editorial analysis

One scoped package per chart type, chosen by you at install time

nivo is not a single chart library you drop into a project. The install step has two halves: a core package, then one scoped package for each chart you want, and the only example given covers bar charts.

code
yarn add @nivo/core @nivo/bar

The README defers the full list to the Components Explorer on nivo.rocks. The real inventory sits in the packages/ directory of the monorepo, which is a pnpm workspace driven by lerna. Nothing in the README hands you a known-good set of packages for a realistic screen, which means the assembly order is yours to verify before the first sprint rather than after it.

SVG, HTML and Canvas are listed as filters, never mapped to charts

The feature list links three filtered views of the same site: SVG charts, HTML charts and Canvas charts, each a query string against the component index. The list tells you all three exist. It does not say which component uses which, that no component offers more than one, or whether the two heavier renderers expose the same props and the same theming surface. That gap has a practical consequence for anyone standardising on a rendering approach. There is no global switch to set, because renderer choice appears to live on the component rather than on the library. If your team assumes one rendering model across a page and you pick charts without checking, you can end up mixing approaches inside a single view, with two different theming paths to keep in sync. The site is where you resolve this, one component at a time, and the README does not hand you a table that would settle it in one pass.

Server side rendering is two Dockerfiles and a Procfile, not an import

The feature list advertises server side rendering and an HTTP API in one line, which reads like a capability you get by importing something. The repository tells a different story. There is a separate api/ directory, a Dockerfile.nivo-api, a second Dockerfile.nivo-website for the documentation site, a Procfile, a deploy/ directory and a DEPLOY_DOCKER.md. The phony target list in the Makefile covers help, bootstrap, init, pkgs-build, pkgs-publish, clean-all, website-install, website, website-build, website-deploy, storybook, storybook-build, storybook-deploy, deploy-all and e2e-open. No target in that list is named for the API. So before you can render a chart on a server you are committing to running a service, and the README gives you no command to start it. Plan for the API as a deployment with its own health checks and scaling decisions, not as a prop you flip, and budget the reading time for DEPLOY_DOCKER.md that the README does not summarise.

The README's install line says yarn, the repository is a pnpm workspace

The documented install command and the repository's own tooling disagree about which package manager owns the project. The README tells consumers to use yarn, while the tree is a pnpm workspace: pnpm-lock.yaml, pnpm-workspace.yaml, an .npmrc and an .nvmrc, and the Makefile's global install target runs the following.

code
pnpm install

lerna ^8.2.2 sits in the root devDependencies alongside a pnpm-lock.yaml, so even for contributors the package manager story has more than one plausible answer. For a consumer this matters less than it sounds, since you only need the published scoped packages. For a fork it matters immediately: a clean rebuild of master will follow the Makefile, not the README, and the two paths can produce different trees. The README also does not document how to move between nivo versions or how to roll back, so if you adopt it, write down the exact version you installed on day one and keep your own lockfile, because nothing in the project will restore that state for you.

Transitions come from react-spring and the README names no way to turn them off

Motion is listed as a feature and attributed to react-spring, with a link out to that library. The README does not document a prop for disabling animation, a reduced-motion branch, a duration setting, or a way to render every chart in its final state on first paint. That absence has consequences for two kinds of reader. If your product has an accessibility policy around motion, or your team requires deterministic server-rendered output for snapshot tests, you cannot satisfy either from the README alone, and the answer has to be dug out of per-component documentation in the playground. And because react-spring is named as the engine behind transitions rather than as an optional add-on, the animation runtime is part of what the animated components pull in. If a chart does not need motion at all, this is still the dependency path you are taking, and you have no documented lever to detach it.

The newest npm release is more than a year older than the newest commit

Two dates in the repository tell different stories about the project's state. The last push to master is 2026-07-21, so work continues. The most recent releases are v0.99.0 from 2025-05-23, v0.98.0 from 2025-05-16 and v0.97.0 from 2025-05-16, and all three landed inside a single week. The repository is not archived and the licence is MIT, so nothing is being withdrawn. But master has moved well past the newest tag, which means the documentation you read on nivo.rocks can describe source you have not got. The failure mode is quiet: a prop or a component documented on the site is simply absent from the version your package manager resolves, and nothing in the error says which side of that gap you are on. Pin the version, check the release you are reading against the release you installed, and treat an undocumented prop as unverified until it works in your build.

Playwright and Cypress in the tree are for the project's own charts, not yours

The root devDependencies show a heavy test stack: cypress ^12.11.0, playwright ^1.52.0, puppeteer ^19.11.1, enzyme ^3.11.0, jest ^29.5.0 and jsdom ^22.0.0, with a cypress/ directory, a storybook/ directory and an ACCEPTANCE_TEST.md at the top level. None of that is exported to you when you install @nivo/core. What you get from the project is a set of tested components, not a harness for testing the charts you compose from them, and the Makefile's e2e-open target belongs to the storybook the maintainers run, not to a consuming app. Two details matter if you plan to contribute rather than just consume. The root pins @types/react at ^18.3.0 while the enzyme adapter is @wojtekmaj/enzyme-adapter-react-17 at a fixed 0.6.6, so the unit test layer is built around a React 17 adapter. And CI is defined in .github/, with the README badge pointing at ci.yml on master, so a fork's local test run is not evidence that your change passes the same gate.

Editorial conclusion

Adopt nivo if your team already works in React and can accept one scoped package per chart family and a per-component choice between SVG, HTML and Canvas. Read the Components Explorer before you commit, because the README will not tell you which package holds which chart, whether the version on npm has the prop you just read about, or how to silence the react-spring transitions.

Frequently asked questions

Is Nivo good for data visualization?

It is a set of React components for building dataviz apps on top of d3, offering SVG, HTML and Canvas charts, server side rendering with an HTTP API, theming, patterns, gradients and responsive charts. Whether it suits you depends on whether you can assemble one scoped package per chart type and live without documented guidance on renderer choice.

Where can I find Nivo documentation?

The documentation, the guides and the interactive components playground are all on nivo.rocks, and the README points to the Components Explorer at http://nivo.rocks/components/ for the full list of packages and components. Guides cover axes, colors, legends, gradients, patterns and theming.

Is Nivo based on React?

Yes. nivo provides React components and is built on top of d3, with the repository written in TypeScript. Motion and transitions are powered by react-spring.

Is Nivo open source?

Yes, the project is MIT licensed, with the licence file at LICENSE.md on the master branch. Funding runs through Open Collective as backers and sponsors, and the README invites donations to support the project.

Official sources

  1. License: MIT
  2. plouc/nivo on GitHub
  3. Project website
  4. README
  5. Releases
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/plouc-nivo.svg)](https://hysenlabs.com/projects/plouc-nivo)

Star history chart for your README

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

Was this useful?