mbrn/material-table

Datatable for React based on material-ui's table with additional features

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 20th, 2026
Created on August 6th, 2018
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 997
Total Stargazers: 3,482 (+0)
Total Subscribers: 45 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 445 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

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

Top labels

  • wontfix (58)
  • question (21)
  • bug (20)
  • feature (13)
  • enhancement (1)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

material-table is a datatable component for React based on Material-UI's table with additional features.

The tool addresses the need for a feature-rich table component that integrates with Material-UI while providing capabilities beyond the base table implementation. It builds on Material-UI's table foundation and adds functionality like inline editing, filtering, sorting, grouping, search, selection, detail panels, custom column rendering, data export, and tree data support. The component handles both local and remote data sources and allows extensive customization through component overriding and styling options.

Teams building React applications with Material-UI should consider this tool if they need a table that supports interactive features out of the box. It works well for applications requiring editable tables, complex data presentation with grouping and filtering, or scenarios where exporting data is important. The project provides a documented homepage with examples and a clear feature list, making it straightforward to evaluate whether specific requirements are met.

The project is undergoing refactoring and testing, with the maintainers explicitly requesting that pull requests be limited to small bug fixes rather than large changes during this period. Issues are prioritized by community reaction count rather than submission order, giving visibility to problems that affect multiple users.