Open-source project
puikinsh/Bootstrap-Admin-Template avatar
puikinsh/Bootstrap-Admin-Template

Metis ships under three names and its npm main is an HTML file

Metis - Free Bootstrap 5 Admin Dashboard Template

2,859 stars1,319 forksHTMLMIT

At a glance

What is it?
Metis is a free Bootstrap 5 admin dashboard template: thirty pages, Alpine.js, Chart.js, dark mode, self-hosted fonts, and a stated goal of zero third-party runtime requests. The seams are in the packaging. The repository is called Bootstrap-Admin-Template, the npm package metis-admin-dashboard, the source tree src-modern and the output dist-modern, and the published package's main entry points at an HTML file.
Who is it for?
Metis suits someone who wants a finished admin surface to rebrand rather than build, and the design decisions are documented rather than implied, which is unusual for a template. Two things to check before you adopt it.
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 6 days ago.
What is it written in?
Mainly HTML, 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

  • puikinsh/Bootstrap-Admin-Template2,859 ★ · +10
Star history
Repository2026-10-042026-11-15
puikinsh/Bootstrap-Admin-Template2.8k2.9k

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

Editorial analysis

Three names for the same template

The repository is named Bootstrap-Admin-Template. The product inside it is called Metis. The npm package is metis-admin-dashboard, and the version in that manifest is 3.7.0, matching the newest release tag.

The directories follow a fourth convention. Source lives in `src-modern/`, build output goes to `dist-modern/`, and the manifest's main entry is `dist-modern/index.html`. Neither modern suffix is explained anywhere in the file a reader sees first, which suggests both predate the current tooling rather than being a deliberate distinction.

The homepage field makes it worse. The manifest points it at the GitHub repository, which is where you already are, while the repository's own page metadata points at the vendor's live preview site instead. Two different values for the same field, in two places, pointing at two different kinds of destination.

The npm package main entry is an HTML file

The manifest declares the package as an ES module and sets publish access to public, so it is meant to be installed from a registry. What it points at is the built HTML page:

code
  "main": "dist-modern/index.html",

An HTML file is not a JavaScript entry point, so nothing can import this package. What an install gives you is the template itself: the manifest's files list includes the whole build output directory, the whole source directory, the public assets directory, the scripts directory and the documentation directory, plus the build configuration files and the changelog and contribution guides.

So the registry route and the git route deliver the same thing, which is a set of files to copy. That is a reasonable choice for a template, and it is worth knowing before anyone adds it to a dependency list expecting a component.

Mock authentication and demo data default to true

The environment example is where the template's defaults are visible, and two of them matter more than the rest. Under a heading for feature flags:

code
VITE_ENABLE_DEMO_DATA=true
VITE_ENABLE_MOCK_AUTH=true

Both are on. So a developer who copies the file as instructed gets an application that fakes its login and serves fabricated records, which is exactly what you want while building a screen and exactly what you do not want on a deployment.

The rest of the file is conventional: a development port and host, an API base URL pointing at a port nothing serves, a request timeout, an icon provider choice between two libraries, an analytics identifier left empty to disable it, a currency and a site name, a date format, a default theme, a chart colour scheme, a notifications switch and a page size.

The file also carries the instruction to copy it to a local env file and never commit that file, which is the right instruction given what sits in it.

The chart library changed twice in two months

The release names carry their own changelog. Version 3.7.0, published on 2026-09-30, is titled as charts moving to Chart.js under an MIT licence, with every chart rebuilt, re-themed live on the light and dark switch, and the chart bundle down from 207 KB to 73 KB gzipped.

The release before it, 3.6.0 from 2026-09-08, is titled a neutral design system, auth and error pages, and ApexCharts 7.

So the previous release shipped one charting library and this one ships another, two months apart, and the measured effect was a two thirds reduction in the chart payload. A third release, 3.5.0 from 2026-08-03, is titled a modernisation pass with zero third-party requests and all advisories patched, which is the release that introduced the self-hosting story.

Three releases in two months, each carrying a migration note in its title, is a fast cadence for a template and it means the README's version notes are the only changelog most users will read.

The palette is checked in code, not by eye

One feature claim is unusually specific: the chart colours come from a single source file, and that file is checked for a lightness band, a chroma floor, colour-blind separation and contrast in both themes.

The path is named in the text, at `scripts/utils/chart-palette.js`. So the colour decisions live in a build-time script rather than in stylesheets, and the checks described are the kind normally done once by a designer and never repeated.

The rest of the design system is stated as rules rather than as a mood. Structure comes from borders rather than shadows, with shadows reserved for things that genuinely float such as dropdowns, modals and the mobile sidebar. A single accent colour is used only for interaction, on primary actions, the active navigation item and focus rings, and semantic colour appears only where it carries meaning.

That is a design system described as constraints, which is the more useful form for anyone extending it.

A README that spends a table on a paid template vendor

Between the feature list and whatever follows it, the file devotes a section headed as professional admin templates to a commercial catalogue. Six products are laid out in an HTML table, each with a title, a one line summary and a link, and every one of those links carries the same three tracking parameters identifying GitHub as the source and Metis as the campaign.

The products are described in specific terms: a React and Tailwind one with nine dashboards and a light and dark toggle, a Bootstrap one with a hundred components and right to left support and ten colour presets, another with a hundred and sixty pages, one with two hundred and fifty elements, a jQuery and Webpack one, and a cryptocurrency dashboard.

None of them is this template. What the section does is convert a free download into a shop window, with attribution on every click. That is a commercial decision rather than a defect, and it is the part of the file a reader evaluating the licence has to notice.

Self-hosting everything is stated as a security property

The stack list gives the versions: Bootstrap 5.3.8, Alpine.js 3.17, Vite 8.2 described as rolldown-powered, Sass 1.104, Bootstrap Icons 1.13.1 and Chart.js 4.5.

Two of those entries are about restraint. Only the chart types actually used are registered with the chart library, and the icon build ships only the roughly one hundred and fifty eight icons in use out of more than eighteen hundred available.

The zero third-party requests claim is the load-bearing one, and the file gives three reasons: fonts, charts, syntax highlighting and images are all served locally, so the template works offline, works behind a strict content security policy, and does not leak visitor addresses to a content delivery network.

That is the argument for the whole approach. A dashboard template is usually a page full of third party scripts, and each one is a dependency you did not choose. This one treats that as the defect to fix.

Editorial conclusion

Metis suits someone who wants a finished admin surface to rebrand rather than build, and the design decisions are documented rather than implied, which is unusual for a template. Two things to check before you adopt it. Read the environment example, because the flags that enable mock authentication and demo data are set to true there, so a copy-pasted setup starts in a mode that is not real. And decide how you will consume it, since the package publishes its build output and the source tree, and the main entry in the manifest is an HTML file, so an npm install is a template download rather than an import.

Frequently asked questions

What is an admin template?

In this repository it is a ready-made dashboard surface: thirty pages including sign in, account creation, password reset, two-step verification, a lock screen and error pages, plus analytics, user, product, order, file, calendar, message, report, settings, security and support screens, built on Bootstrap 5 with Alpine.js and Chart.js.

Is there a template for an admin panel in Bootstrap?

That is a question about the category rather than about this project. This repository is one Bootstrap 5 template of that kind, distributed free under MIT and published to a package registry alongside its source and build output, with a live preview hosted by the template vendor.

What are Bootstrap templates used for?

The file does not discuss the category in general. What it describes for its own template is the feature set: a design system built on CSS custom properties, dark and light mode with local storage persistence, a responsive layout, a chart palette validated for contrast and colour-blind separation, and a build pipeline with hot module replacement and optional TypeScript.

What is Bootstrap and why is it used?

The repository uses Bootstrap 5.3.8 as its component and layout foundation, and adds its own design system on top through CSS custom properties, a single accent colour reserved for interaction, and borders rather than shadows for static structure. It does not explain what Bootstrap is for projects other than its own.

How do I run the Metis template locally?

Copy the environment example to a local env file and do not commit it, then use the dev script, which runs the build tool in development mode, with a host variant that exposes it on the network. The example sets the development port to 3000, the host to localhost, and turns on both demo data and mock authentication.

Official sources

  1. License: MIT
  2. Project website
  3. puikinsh/Bootstrap-Admin-Template on GitHub
  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/puikinsh-bootstrap-admin-template.svg)](https://hysenlabs.com/projects/puikinsh-bootstrap-admin-template)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/puikinsh-bootstrap-admin-template.svg)](https://hysenlabs.com/projects/puikinsh-bootstrap-admin-template)

Was this useful?