Open-source project
carbon-design-system/carbon avatar
carbon-design-system/carbon

Carbon Design System: IBM's Open Source UI Toolkit for React and Web Components

A design system built by IBM

9,631 stars2,306 forksTypeScriptApache-2.0

At a glance

What is it?
Carbon is IBM's open source design system, a monorepo of React and web component libraries, Sass styles, design tokens, icons, and tooling. This review covers what it offers, how it is structured, and where its complexity may be a drawback.
Who is it for?
Adopt Carbon if you are building a product that must align with IBM's visual language or if your team already uses IBM Plex and the associated grid and motion tokens. It is a poor fit for small projects that need a lightweight component set, because the monorepo and the number of packages add overhead.
Can I use it commercially?
Yes. Apache-2.0 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 3 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

  • carbon-design-system/carbon9,631 ★ · +246
Star history
Repository2026-08-262026-11-19
carbon-design-system/carbon9.4k9.6k

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

Editorial analysis

What Carbon Solves and Who It Targets

Carbon solves a specific problem: giving product teams a coherent set of UI components, styles, and assets that all follow the same visual language. IBM built it for its own products, but it is open source under Apache-2.0. The intended audience is development teams that need to ship interfaces quickly without inventing a design system from scratch. If your product must look like it belongs to the IBM ecosystem, or if you want a battle-tested system with a large component inventory, Carbon is a direct answer. The README lists React and web components libraries, plus Sass styles, design tokens, icons, pictograms, and tooling. That breadth means it is not a single library but a family of packages, each with a specific role.

The Monorepo Structure and Package Breakdown

The repository is a monorepo, which is evident from the package list. The core packages are @carbon/react for React components and styles, and @carbon/web-components for standards-based web components. Around those sit foundation packages: @carbon/colors for color scales, @carbon/elements for IBM Design Language foundations, @carbon/grid for layout, @carbon/icons for icon assets, @carbon/layout for spacing tokens, @carbon/motion for motion curves, @carbon/pictograms for pictogram assets, @carbon/styles for Sass styles, @carbon/themes for theme tokens, and @carbon/type for type tokens paired with IBM Plex. This separation lets you install only what you need. For example, a project that only needs color tokens can pull @carbon/colors without the full component library. But it also means you have to understand which package does what, which adds a learning curve.

React vs. Web Components: Two Front-End Paths

Carbon offers two distinct implementation routes. The React library, @carbon/react, is for teams building with React and includes components and styles. The web components library, @carbon/web-components, is standards-based, meaning it works with any framework or with no framework at all. This dual approach is a key architectural decision. If you are locked into React, the React package gives you a smoother integration with props and state. If you need framework-agnostic components, web components are the way. The README also mentions community-maintained packages for Angular, Svelte, and Vue, which shows that the ecosystem extends beyond the official monorepo. However, those community packages are not maintained by IBM, so you should evaluate their maturity separately.

Getting Started: Installation and First Steps

The README does not include installation commands, but the package list implies the typical npm workflow. You would install the package you need, for example npm install @carbon/react for a React project, or npm install @carbon/web-components for a web component project. The documentation links point to the official site for getting started guides. For styling, @carbon/styles is the Sass package, so you would import it into your Sass pipeline. The themes package, @carbon/themes, provides tokens for color systems, and you can switch themes by changing token values. The migration guide is linked from the README, which suggests that moving from older versions requires planning. The release cadence is active, with v11.119.0 released on 2026-10-21, so you can expect regular updates.

Design Tokens and Theming: The Foundation of Consistency

Carbon's design tokens are spread across several packages. @carbon/themes handles theme tokens for color systems, @carbon/type provides type tokens designed to pair with IBM Plex, and @carbon/layout gives layout units and spacing scale tokens. This token-based approach means you can apply a consistent spacing and typography system across your application. The @carbon/motion package defines productive and expressive motion curves, which allows for consistent animation behavior. The separation of concerns is a strength: you can adopt just the tokens without the components, or use the components with your own tokens. The downside is that the token system is tied to IBM's design language, so if you need to deviate significantly from IBM's aesthetic, you will be fighting the token values.

Icons and Pictograms: Asset Packages with Framework Variants

The @carbon/icons package provides icon assets, and it has separate framework packages for React and Vue: @carbon/icons-react and @carbon/icons-vue. This means you can import icons directly as components in your chosen framework. Similarly, @carbon/pictograms offers pictogram assets with a React variant. The README lists these as separate packages, so you can install them independently. This modularity is convenient, but it also means you have to manage multiple dependencies if you need icons, pictograms, and components. The icon set is designed to match the Carbon style, so it will look consistent with the rest of the system. If you need custom icons, you would have to create them separately.

Limitations and Cases Where Carbon Is the Wrong Tool

Carbon is not a lightweight solution. The monorepo contains many packages, and even the core React library is substantial. For a small project or a prototype, the overhead of learning the token system and the component API may not be worth it. The design language is unmistakably IBM, which can be a mismatch if your brand requires a different look. The web components library is standards-based, but the README does not detail browser support, so you should verify that it works in your target browsers. Another limitation is the dependency on IBM Plex for type tokens; if you cannot use that font, the typography will not match the intended design.

Alternatives: How Carbon Differs from Other Design Systems

A direct alternative is Material UI, which is built for React and follows Google's Material Design. Carbon separates tokens into packages like @carbon/themes and @carbon/type, which gives you more granular control. Another alternative is Ant Design, which is also React-focused and offers a large component set. Ant Design uses its own design language, so the visual style is distinct. The main difference is that Carbon is tied to IBM's design language, while Material UI and Ant Design are more generic. If you need a design system that is not tied to a specific corporate brand, those alternatives might be more flexible.

Maintenance and License Considerations

The repository is actively maintained, with a recent release (v11.119.0 on 2026-10-21) and a regular release cadence. The CI workflow is present, and the project is not archived. This suggests ongoing support. The license is Apache-2.0, which is permissive and allows commercial use, modification, and distribution, but you should review the license terms yourself. The README mentions a code of conduct and contribution guidelines, which indicates a structured community process. The migration guide is a positive sign for upgrade paths, but it also implies that breaking changes can occur between major versions. The community is active on GitHub Discussions and Discord, so you can get help, but the maintenance effort for your team will depend on how closely you follow upstream releases.

Editorial conclusion

Adopt Carbon if you are building a product that must align with IBM's visual language or if your team already uses IBM Plex and the associated grid and motion tokens. It is a poor fit for small projects that need a lightweight component set, because the monorepo and the number of packages add overhead. Before adopting, verify that the React or web components package covers the components you need, and check the migration guide if you are coming from an older Carbon version. The Apache-2.0 license is permissive, but you should confirm that the design tokens and fonts meet your brand requirements, as they are tuned to IBM.

Frequently asked questions

What does the Carbon monorepo contain?

It holds the React and web components libraries plus Sass styles, design tokens, icons, pictograms, and the tooling used to build with Carbon, organized as a Yarn workspace covering the actions, config, and packages globs.

Can I install the carbon package directly from npm?

No. The root package.json is marked private at version 0.0.0, so the name carbon is reserved for the workspace and consumers depend on scoped packages such as @carbon/react or @carbon/styles instead.

Which frameworks have Carbon bindings shipped from this repository?

Only React and web components, through @carbon/react and @carbon/web-components. Angular, Svelte, and Vue are described as community maintained and live in separate repositories outside the workspace globs.

What Node version does Carbon require?

The root manifest sets engines.node to >=20.x, and the repository ships an .nvmrc alongside a .yarnrc.yml and a committed yarn.lock for the Yarn workspace.

How do I run Carbon's end to end tests?

The test:e2e script runs jest inside a cross-env wrapper that sets BABEL_ENV=test and passes jest.e2e.config.js instead of the default config, with playwright.config.js and an e2e directory at the root.

Where do I find guidance for migrating a major Carbon version?

The Migrate link points to carbondesignsystem.com/migrating/guide/overview/, and the examples directory includes incremental-migration-vite/ and v10-token-compat-in-v11/ as working starting points.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
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/carbon-design-system-carbon.svg)](https://hysenlabs.com/projects/carbon-design-system-carbon)

Star history chart for your README

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

Was this useful?