c3js/c3

:bar_chart: A D3-based reusable chart library

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 7th, 2026
Created on July 18th, 2013
Open Issues & Pull Requests: 772 (+0)
GitHub issues: Enabled
Number of forks: 1,361
Total Stargazers: 9,349 (+0)
Total Subscribers: 260 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.5 days
Mean response time: 247.1 days
90th percentile: 199.0 days
Tracked items: 10

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 2,278 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (2)
  • resolved maybe (2)
  • C-bug (1)
  • C-feature-request (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

C3 is a D3-based reusable chart library that enables deeper integration of charts into web applications.

C3 solves the problem of building interactive charts by providing a higher-level abstraction over D3.js. Rather than writing low-level D3 code directly, developers define charts through a configuration-based approach that leverages D3's rendering capabilities underneath. This allows charts to be embedded and manipulated more easily within web applications while retaining access to D3's power for customization.

C3 suits projects where you need interactive, SVG-based charts with a simpler API than raw D3 but want to avoid the overhead of heavier charting libraries. It works well for applications requiring reusable chart components that can be updated dynamically. The library requires D3.js as a dependency, so adoption makes sense in projects already using or comfortable with the D3 ecosystem.

The project maintains active community channels including a Google Group for general discussion and a Gitter chat, with the issue queue reserved for bug reports and feature requests rather than general support. The README emphasizes thorough issue searching and reproduction steps before reporting problems, and requests that pull requests be preceded by issue discussion to confirm desirability. The master branch contains active development commits, indicating ongoing work on the codebase.