Open-source project
wenzhixin/bootstrap-table avatar
wenzhixin/bootstrap-table

Bootstrap Table's data-attribute config, dist entry points, and two-repo dev setup

An extended table for integration with some of the most widely used CSS frameworks. (Supports Bootstrap, Semantic UI, Bulma, Material Design, Foundation, Vue.js)

11,813 stars4,331 forksJavaScriptMIT

At a glance

What is it?
Bootstrap Table turns a plain HTML table into one with sorting, pagination, row selection, card view, and detail view, configured through data attributes. It is MIT licensed and was pushed on 2026-10-03, but nearly all of its actual option surface lives on a separate docs site and a separate examples repository, not in the repository you clone.
Who is it for?
Bootstrap Table fits teams that already ship Bootstrap and want sorting, pagination, and row selection without hand-building a grid, and the MIT license makes a trial cheap. It is a poor fit if you need the option list inside your own source tree, if you need to know exactly what ships inside dist, or if nobody can host a live example.
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 received new commits within the last day.
What is it written in?
Mainly JavaScript, 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

  • wenzhixin/bootstrap-table11,813 ★ · +1
Star history
Repository2026-09-222026-11-15
wenzhixin/bootstrap-table11.8k11.8k

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

Editorial analysis

Data attributes, not an options object, carry the whole configuration

The feature list includes "Fully configurable" and "Via data attributes", so options can be set in markup. The same list names what those options reach: show and hide handled separately for columns, headers, and footers, single or multiple row selection, pagination, detail view, card view, localization, radio and checkbox inputs, column formatting, sorting on a click, a scrollable table with fixed headers, and JSON data pulled over AJAX.

When a column refuses to sort, the attributes in your markup are the only evidence you hold, and the documentation site becomes the place you have to go confirm the spelling.

Default branch develop, but the manual download link asks for master.zip

The repository's default branch is develop. The manual download step points at the source archive instead, and that archive address ends in master.zip, with the Releases page offered as the other manual route. Two branch names in one project is the whole issue. An archive address names a branch rather than a release, so the zip holds whatever that branch contained on the day you fetched it and nothing in the path records a version number. Versions live somewhere else entirely, in a Change Log file at the repository root.

That difference is invisible on the package manager routes. A version resolves to an artifact that was published once, so these two commands give you something identified:

bash
yarn add bootstrap-table
bash
npm install bootstrap-table

The archive route and the CDN routes promise no such thing. Three CDNs are named, cdnjs, bootcss, and jsdelivr, and each is a third party deciding when to pull an update, with no pinning scheme documented. Check the dates before trusting any route. The last push on this repository is 2026-10-03. The three most recent releases are 1.28.0 on 2026-10-28, 1.27.3 on 2026-04-23, and 1.27.2 on 2026-04-15.

The published tarball ships src and index.d.ts, but no site, tests, or cypress

package.json sets type to module, so the published package is an ES module, and its main and style fields point at built output rather than at source you compile. main resolves to dist/bootstrap-table.min.js and style resolves to dist/bootstrap-table.min.css, meaning what your bundler imports is a prebuilt file. A third field, sass, points at src/bootstrap-table.scss, which is the single path back into the source tree. Take it and the stylesheet your users download becomes output you own and must rebuild on every upgrade.

The files array decides what travels to a registry, and the list is short. It carries dist/, src/, CHANGELOG.md, README.md, LICENSE, bower.json, bootstrap-table.jquery.json, composer.json, index.d.ts, and package.json, while explicitly excluding src/.babelrc. The documentation source is not on that list even though directories maps doc to site, and neither are the cypress directory, the tests directory, or the tools directory. You can read the example site on GitHub, not from the tarball your dependency manager already cached. index.d.ts does ship, so TypeScript users get declarations without installing a second package.

bower.json, composer.json, and a jQuery manifest ship beside package.json

Three manifests from older packaging eras sit in the same files list as the modern one. bower.json is there, composer.json is there, and bootstrap-table.jquery.json is there. The repository root also carries a yarn.lock with no npm lockfile beside it. The README's How to get it section gives only the two package manager commands quoted earlier and does not mention these manifests.

The yarn.lock without an npm lockfile matters for contributors: npm installs resolve floating ranges and land on whatever satisfies them that day.

Local development clones two repositories and then fixes the port

Developing the plugin locally is not a single clone. The documented sequence creates a directory, enters it, clones the plugin repository, clones a separate bootstrap-table-examples repository, adds a static server, and runs it:

bash
mkdir bootstrap-table-dev
cd bootstrap-table-dev
git clone https://github.com/wenzhixin/bootstrap-table
git clone https://github.com/wenzhixin/bootstrap-table-examples

yarn add http-server
npx http-server

Both clones sit in that block and the second is not optional there, since the examples repository is what serves the pages. The outcome is also a fixed address: the instruction ends by opening http://localhost:8081/bootstrap-table-examples, so port 8081 is where this setup lives and nothing describes changing it. Anything else on your machine already holding that port collides with the documented path.

Building is a separate act from serving, and it is offered twice, once per package manager, with a note to use a current version of either tool. Output lands in a dist directory:

bash
yarn install
yarn build
bash
npm install
npm run build

Notice that the local develop recipe reaches for yarn to add the server while the build recipe offers npm as an equal alternative. The two halves of the workflow are not symmetrical, and the served pages come from the examples clone, not from the plugin clone you just built.

A bug report is expected to arrive with a live URL attached

The project's answer to a bug report is an address, not a paragraph. Contributors are pointed at CONTRIBUTING.md before anything else, and the issue guidance asks for an online example built through an online editor, including a template reachable from a Load Examples button. The stated reason is saved time. The practical effect is a filter, because a report that cannot be reduced to a live page forces a maintainer to rebuild the case by hand, and assembling that page is not small when the configuration surface runs as deep as the feature list suggests.

The README lists no private channel. Help goes to a StackOverflow tag and a SegmentFault tag, both public and both searchable, which helps you find an answer and hurts when the problem involves unreleased code or a private schema. Before spending an afternoon on a reduced case, know that you are writing into a public archive rather than opening a ticket, and know too that the project asks for a star and calls that support its biggest motive force.

Extensions are named in the description and never named anywhere else

Extensions appear twice in this project and are identified zero times. The word shows up in the README's opening line, where the table is described as carrying extensions among its added features, and again as the closing bullet of the feature list. The README names no extension, file path or code sample for them. The only pointers out are the documentation site and the separate examples repository.

That gap is expensive for anyone auditing a dependency. If the extension mechanism ships inside the dist files that main and style point at, then a vendored copy carries code you cannot enumerate from the project metadata, and there is no way to learn which parts are unused before shipping. If the extensions are separate artifacts, the metadata still gives you no list to check against, so the answer lives only in the example repository. Neither the files array nor the top-level listing settles it.

The same flatness applies to the framework claim. The repository description says the table integrates with Bootstrap, Semantic UI, Bulma, Material Design, Foundation, and Vue.js, while the description field inside package.json stops at Foundation and drops Vue.js.

Editorial conclusion

Bootstrap Table fits teams that already ship Bootstrap and want sorting, pagination, and row selection without hand-building a grid, and the MIT license makes a trial cheap. It is a poor fit if you need the option list inside your own source tree, if you need to know exactly what ships inside dist, or if nobody can host a live example. Before adopting it, pin an exact version instead of tracking the branch, read the options on the docs site rather than in the README, and check the Change Log for what landed after your pinned release.

Frequently asked questions

How do you use Bootstrap Table in an HTML page?

You add a plain HTML table and configure it through data attributes, then load one of the build files. The four acquisition routes are the Releases page or the source archive, yarn add bootstrap-table, npm install bootstrap-table, or a CDN such as cdnjs, bootcss, or jsdelivr. Documentation sits at bootstrap-table.com and runnable examples live in a separate bootstrap-table-examples repository.

What is Bootstrap Table?

It is an extended Bootstrap table with radio, checkbox, sort, pagination, and extensions added on top. The repository description says it integrates with Bootstrap, Semantic UI, Bulma, Material Design, Foundation, and Vue.js. The license is MIT.

How does Bootstrap Table compare with DataTables?

No comparison appears in this project's files. The repository only points at its own documentation site, the bootstrap-table-examples repository, a StackOverflow tag, and a SegmentFault tag for questions. Making the comparison yourself means reading the options on the docs site, since the README does not enumerate them.

Is Bootstrap end of life, and what does that mean for Bootstrap Table?

The repository does not discuss the lifecycle of the underlying CSS framework. What it does record is its own activity: it is not archived, the last push is dated 2026-10-03, and the latest releases are 1.28.0 from 2026-10-28, 1.27.3 from 2026-04-23, and 1.27.2 from 2026-04-15.

What is the scope of Bootstrap Table on a page?

The project does not define scope. What it lists is show and hide for columns, headers, and footers, single or multiple row selection, pagination, card view, detail view, localization, and extensions. Scope in the CSS sense is not mentioned in the repository files.

What is the alternative to react-bootstrap-table-next?

This repository does not name an alternative. It points to bootstrap-table.com for documentation, to a separate examples repository, and to public help tags on StackOverflow and SegmentFault. Its own description claims support for Vue.js among the CSS frameworks it integrates with, which is the closest thing to a positioning statement present.

Official sources

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

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/wenzhixin-bootstrap-table.svg)](https://hysenlabs.com/projects/wenzhixin-bootstrap-table)

Was this useful?