phpMyAdmin: a 5.2.3 stable line, a 6.0.0-dev master branch, and why a Git checkout is not an install

A PHP web front end, not a database server

phpMyAdmin is a web interface for MySQL and MariaDB. It is a PHP application that you host on a web server and point at a database; it does not replace the database. That distinction answers one of the most common questions about it: MySQL or MariaDB stores and serves the data, and phpMyAdmin is the browser front end you use to work with it.

The project is licensed under GPL-2.0 and is not archived. The last push to the repository landed on 2026-11-01. The web front end is assembled from a long list of browser libraries in package.json, including Bootstrap 5.3, jQuery and jQuery UI, Chart.js with a zoom plugin, CodeMirror 5.65.12 and OpenLayers (`ol`). The top-level `index.php` and the `public/`, `app/`, `src/` and `resources/` directories hold the application, with `docs/` carrying the documentation source that is also published on Read the Docs.

master is 6.0.0-dev while the latest release is 5.2.3

The repository uses three kinds of names, and picking the wrong one changes what you run. `STABLE` is the current stable release. `master` is the development branch. Releases are tagged with underscores, so version 5.0.1 is `RELEASE_5_0_1`, and the most recent tags are `RELEASE_5_2_3` (2025-10-08), `RELEASE_5_2_2` (2025-01-21) and `RELEASE_5_2_1` (2023-02-08).

The package.json on master already reads `"version": "6.0.0-dev"`, and a CHANGELOG-6.0.md sits at the top level. So cloning the default branch gives you an unreleased major version, not the 5.2.3 that the website offers for download. For anyone setting up phpMyAdmin on a server that other people depend on, that means checking out `STABLE` or a release tag, or using the release download, rather than taking whatever `master` contains on the day you clone it. Reading CHANGELOG-6.0.md before a future upgrade is the cheapest way to learn what the next major version changes.

Running from Git means running Composer and a Node 22 build yourself

The newest release is offered at phpmyadmin.net. If you follow the Git repository instead, the checkout is not ready to serve. phpMyAdmin manages its PHP library dependencies with Composer, and with Git development versions you have to run Composer manually; the installation guide on docs.phpmyadmin.net has a section on installing from Git.

The front end adds a second build. package.json requires Node 22 or newer and pulls in Babel, webpack loaders, Sass 1.78.0, PostCSS with autoprefixer, and rtlcss for right-to-left layouts. With `webpack.config.cjs`, `babel.config.json`, `tsconfig.json` and a `yarn.lock` at the root, the JavaScript and CSS are compiled from source rather than committed ready to use. The consequence is that a server which only has PHP installed cannot run a fresh Git checkout as it stands; you need Composer and a recent Node toolchain somewhere in the build, or you should use a release package.

Stable releases arrive years apart

The release history is sparse. 5.2.1 came out on 2023-02-08, 5.2.2 followed almost two years later on 2025-01-21, and 5.2.3 arrived on 2025-10-08. Meanwhile, master has moved on to 6.0.0-dev and the repository keeps receiving commits.

For operators this cuts two ways. A long-lived release line means fewer forced upgrades. It also means that improvements made on master can sit unreleased for a long time, and features you see discussed in the repository may not be in the version you can download. If you need something that only exists on master, the honest options are to wait for 6.0 or to run a development build with the Composer and Node steps that come with it. For security questions, the project points to a dedicated page at phpmyadmin.net/security rather than the issue tracker, and that is the page to check against your installed version.

config.sample.inc.php and the signon and many-hosts examples

Configuration starts from `config.sample.inc.php` at the repository root. The `examples/` directory adds four files that show more specialised setups by name: `config.manyhosts.inc.php`, `openid.php`, `signon.php` and `signon-script.php`. The file names are the guide here: one for many hosts, one for OpenID and two for signon, and the documentation explains the matching settings.

These examples are starting points, not a guided setup. The repository README itself stays short and sends readers to docs.phpmyadmin.net for setup details, and to the `docs` folder in the repository for the same documentation offline. Anyone hunting for a default password or a standard login page should go to the setup documentation rather than expect the repository front page to cover it, since the README is mostly badges, branch names and links.

Nine quality badges: PHPUnit, Selenium, mutation and type coverage

The README opens with a row of status badges that show how the code is checked. There is a test suite workflow and a separate end-to-end workflow run with Selenium. Coverage goes to Codecov, code quality to Scrutinizer, type coverage to Shepherd, and a mutation score to the Stryker dashboard. The project also carries a CII Best Practices badge under project 213.

The configuration files at the root match those badges: `phpunit.xml` for tests, `phpstan.neon.dist` with `phpstan-baseline.neon` and `psalm.xml` with `psalm-baseline.xml` for static analysis, `infection.json5.dist` for mutation testing, `phpcs.xml` for coding style, and on the JavaScript side `jest.config.cjs`, ESLint, JSHint and Stylelint configs. The presence of baseline files for both PHPStan and Psalm means the static analysis runs against a recorded list of accepted findings, which is worth knowing before you read a passing check as a clean bill of health.

Translations live on Weblate, contributions go through CONTRIBUTING.md and a DCO

phpMyAdmin is translated on Hosted Weblate, and the README badge links to its translation status; a `.weblate` file sits at the repository root. The project asks translators to work there. The front-end build also includes rtlcss and its webpack plugin for right-to-left layouts.

Code contributors are pointed to CONTRIBUTING.md and to the contributing page on the website. The repository also ships a DCO file and a CODE_OF_CONDUCT.md. Support requests go through the support page on phpmyadmin.net rather than the code repository. For a newcomer, the practical route is: read CONTRIBUTING.md, base work on `master` since it is the development branch, and set up the Composer and Node build described above, because a development checkout does not run without it.

Editorial conclusion

phpMyAdmin suits anyone who wants to manage MySQL or MariaDB from a browser and is comfortable hosting a PHP application. Production installs should come from a release download or the STABLE branch, not from master, which is 6.0.0-dev. Before you deploy, check which release you are on against the security page at phpmyadmin.net, since stable releases come years apart and a point release can be the one that matters.

Frequently asked questions

Official sources

1. License: GPL-2.0
2. phpmyadmin/phpmyadmin on GitHub
3. Project website
4. README
5. Releases