CLI tool
chart-kit/react-native-chart-kit avatar
chart-kit/react-native-chart-kit

React Native Chart Kit v2: what the /v2 entry point actually changes

Beautiful charts for React Native. Line, area, bar, pie, donut, progress, and contribution heatmaps for dashboards, reports, and data-rich mobile apps.

3,111 stars674 forksTypeScriptMIT

At a glance

What is it?
React Native Chart Kit renders line, area, bar, pie, donut, progress and contribution heatmap charts for iOS and Android apps. The v2 import is the part worth understanding before you migrate a screen.
Who is it for?
Adopt it for dashboard, report and analytics screens where a small set of standard chart types rendered with react-native-svg is enough. Do not adopt it if you need candlestick, radar, realtime or combo charts, or PNG and SVG export: the README places those behind Chart Kit Pro, a licensed product with separate installation and pricing pages.
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 76 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 19, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • chart-kit/react-native-chart-kit3,111 ★ · -2
Star history
Repository2026-09-252026-11-19
chart-kit/react-native-chart-kit3.1k3.1k

-2 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Who React Native Chart Kit is for

The problem is narrow and specific: a React Native screen needs a chart, and the team does not want to hand-write SVG paths, axis ticks and touch handling for it. React Native Chart Kit covers that case with a fixed set of chart types. The README lists line, area, bar, pie, donut, progress and contribution heatmap as the modern public charts, plus tap selection, shared tooltips and crosshairs for mobile interaction, and shared themes with SVG renderer defaults.

The audience is mobile product teams building dashboards, reports and data-rich apps, which is how the package description frames it. If your data lives in a backend and arrives as an array of points, and the screen is a phone or tablet, this fits. If you are building a desktop web dashboard, this is the wrong library: the rendering target is React Native, and the peer dependency is react-native-svg, not a browser DOM.

The v2 import and how a chart is wired up

The mechanism visible in the README is declarative and data-first. You pass an array of objects, plus xKey and yKey naming the fields to plot, and width and height in pixels. The component maps those fields onto an SVG scene under the hood, using react-native-svg as the renderer. There is no canvas, no imperative draw call, and no separate chart instance to keep in a ref.

The design decision that matters most is the split entry point. The README states that the root import stays available for legacy screens, and that new screens should use react-native-chart-kit/v2. The package.json exports map confirms this with two entries: "." pointing at ./dist/index.js and "./v2" pointing at ./v2/index.js, each with its own TypeScript declaration file. That means a codebase can carry both generations at once, and the import path is what decides which one a file gets. It also means a search-and-replace migration is risky unless you know which files are already on v2.

The README points to two migration documents for existing apps, one for moving from v1 and one for prop mapping. It does not reproduce that mapping in the README itself, so the prop-level differences are only documented on the site.

Installing React Native Chart Kit and drawing a first line chart

The README gives two install paths. For a bare React Native project, install the chart package and react-native-svg together:

bash
npm install react-native-chart-kit react-native-svg

For Expo, the README splits the two commands, because react-native-svg is a native module and Expo wants to pick the version that matches your SDK:

bash
npm install react-native-chart-kit
npx expo install react-native-svg

The first chart example in the README uses the v2 entry point and an array of records. Here it is as given, with the data reduced to two points:

tsx
import { LineChart } from "react-native-chart-kit/v2";

const data = [
  { month: "Jan", revenue: 52 },
  { month: "Feb", revenue: 86 }
];

export function RevenueChart() {
  return (
    <LineChart
      data={data}
      xKey="month"
      yKey="revenue"
      width={410}
      height={240}
    />
  );
}

What you should see is a line chart with months along one axis and revenue along the other, sized to the width and height you passed. The dimensions are literal pixels, not percentages, so a chart that looks right on one device width will not fill a wider screen without you measuring it yourself.

The README also documents a documentation CLI, which is unusual for a charting package and useful when you are working offline or from an agent. It ships from version 7.0.4 and needs no API key:

bash
npx --package=react-native-chart-kit chart-kit docs /docs/react-native/charts/line

Run it without a path to list pages, or add --json for structured output. Note what this does and does not do: the README states that charts render locally in your application, and that the HTTP API serves documentation. The CLI is a docs reader, not a rendering service.

Where the free package stops

The clearest limitation is the chart catalogue. Candlebar, radar, realtime bar and combo charts are listed under Chart Kit Pro, along with PNG and SVG export APIs for reports, sharing and background rendering. If your product needs a candlestick view or a chart you can export as an image, the open package is not the whole answer, and the README links to separate Pro installation and pricing pages rather than describing terms inline.

There is a second boundary that is easy to miss. The README does not document rollback. If a v2 migration breaks a screen, the documented path back is the legacy root import, which the README says stays available, but there is no stated deprecation timeline for it. Plan the migration with that uncertainty in mind rather than assuming the root import survives indefinitely.

A third constraint is structural. The package is a rendering layer for data you already have. There is no data fetching, no aggregation, no time-bucketing and no caching described in the README. If your chart needs downsampled server data, that work happens before the array reaches the component.

How it compares with other React Native chart options

The related searches around this project name two directions worth separating.

React-native-gifted-charts is the closest like-for-like alternative: another React Native charting component set aimed at the same screens. The practical difference to check is the prop surface and which chart types ship in the free package, since both projects put some things behind a paid tier. Neither README is reproduced here, so compare the two chart catalogues directly before choosing.

React-native-charts-wrapper takes a different route entirely. It wraps the native charting libraries on each platform rather than drawing SVG in JavaScript. That is the real architectural fork: native rendering versus an SVG scene managed by react-native-svg. Native wrappers can behave differently across iOS and Android and tie you to the native library's configuration model, while the SVG approach keeps one rendering path and one set of props. The trade-off is that SVG work runs on the JavaScript side of the bridge, which is a constraint worth measuring on your own low-end target devices rather than assuming either way.

The broad "what is the best charting library for React Native" question has no single answer, because the answer depends on whether you need native rendering, a paid export API, or just a line chart on a settings screen. For the last case, this package is a reasonable default.

Licence, releases and the cost of upgrading

The package is MIT licensed, and the repository carries a LICENSE file at the top level. That covers the open package. It does not cover Chart Kit Pro, which the README describes as licensed chart workflows with its own installation and pricing pages. If you plan to use candlebar, radar, realtime or combo charts, or the export APIs, treat that as a separate commercial decision rather than assuming the MIT grant extends to it. This is a description of what the README says, not legal advice.

On maintenance, the last push to the default branch was on 2026-09-06, and the most recent release, v7.0.4, carries the same timestamp. v7.0.3 landed minutes earlier on the same day, and v7.0.2 before that on 2026-07-09. The repository is not archived.

The upgrade cost is concentrated in the v1 to v2 move. Because both entry points ship in the same package and the exports map resolves them by path, an upgrade is not forced on you by installing a new version. That is a genuine advantage for large apps: you can move one screen at a time and leave the rest on the root import. The counterweight is that two generations of the same chart component can coexist in one codebase, which is the kind of thing that quietly becomes permanent. The README points to prop mapping documentation precisely because the props differ, so budget time for reading it per chart type rather than per package.

Editorial conclusion

Adopt it for dashboard, report and analytics screens where a small set of standard chart types rendered with react-native-svg is enough. Do not adopt it if you need candlestick, radar, realtime or combo charts, or PNG and SVG export: the README places those behind Chart Kit Pro, a licensed product with separate installation and pricing pages. Before committing, check the migration and prop mapping pages for the components you already use, and confirm which of your imports resolve to react-native-chart-kit/v2 rather than the legacy root.

Frequently asked questions

How do I install React Native Chart Kit?

Run npm install react-native-chart-kit react-native-svg. In an Expo project the README splits this into npm install react-native-chart-kit followed by npx expo install react-native-svg, so Expo picks a compatible version of the native SVG module.

What is a React Native Chart Kit alternative?

The related searches point at react-native-gifted-charts, which is another React Native charting component set, and react-native-charts-wrapper, which wraps the native charting libraries on each platform instead of drawing SVG. The architectural difference is native rendering versus an SVG scene rendered through react-native-svg.

Does React Native Chart Kit work with Expo?

The README gives a separate Expo install path using npx expo install react-native-svg after installing the chart package, which is the standard way to keep a native module aligned with your Expo SDK version.

Official sources

  1. chart-kit/react-native-chart-kit on GitHub
  2. License: MIT
  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/chart-kit-react-native-chart-kit.svg)](https://hysenlabs.com/projects/chart-kit-react-native-chart-kit)

Star history chart for your README

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

Was this useful?