mdbtools
v1.0.1 open-sourceThe section your link pointed to isn't on mdbtools's page any more, so we've brought you to the top.
Set of utilities and libraries for reading and exporting data from Microsoft Access (MDB/ACCDB) files.
mdb-export -t . input.mdb mdb-sql "SELECT * FROM \"My Table\" WHERE col > -1.5"
Summary
mdbtools is an open-source set of command-line utilities and libraries for reading and exporting data from Microsoft Access (MDB/ACCDB) database files, free to use. Commands like mdb-export, mdb-json, and mdb-schema pull tables out as CSV, JSON, or SQL DDL, with libmdb and libmdbsql available for programs that need direct or SQL-style access instead of shelling out. It suits developers and data engineers who need to get data out of legacy Access files on Linux or Unix systems without owning a Windows/Access license, and its README frames it as the toolkit for that job rather than an Access replacement. Development stretches back to 2000 with 87 contributors, but activity has slowed sharply, with just two commits in the past year and the last release over 600 days ago.
Set of utilities and libraries for reading and exporting data from Microsoft Access (MDB/ACCDB) files.
How mdbtools helps
What tables and structure does this legacy Access file actually contain?
prints the version and schema as DDL, listing tables and columns without needing Access installed to open the file first
How do I get the rows out of this Access table and into something my pipeline can read?
exports a table to CSV or JSON so downstream scripts can consume it directly
Which table should I query, and how many rows am I dealing with before I commit to exporting it?
dumps table names and row counts, cheap checks usable in shell scripts before running a full export
What queries were saved inside this database, and what do they actually select?
lists and prints the queries stored in the file, showing their logic without opening Access
Can I run a quick SQL statement against this file without writing an export script first?
runs a SQL engine directly against the file so ad hoc questions get answered on the spot
Will the schema I generate load cleanly into another database engine?
writes the table definitions as DDL, including index and primary key output, for feeding into a SQL import
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for mdbtools, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail mdbtools puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
9 entries
No entries match these filters.
- December 20241
- October 20211
- August 20211
- May 20211
- February 20211
- January 20211
- December 20201
- September 20202
Project health
Issue, contributor and maintainer activity in mdbtools/mdbtools, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 +2 vs prior 12 months
- Maintainers 1 +2 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 43 days first maintainer reply 43 days
- Open backlog 79 of 274 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 79
- Contributors / month 3
- Commits / month 5
- Stars 1,173
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.