Skip to content
Back to search

whodb

Where data access meets operational intelligence

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/clidey/whodb with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/clidey/whodb'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/clidey--whodb/badge.svg)](/listings/clidey--whodb)

HTML

<a href="/listings/clidey--whodb"><img src="/api/listings/clidey--whodb/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Run WhoDB with Docker:

docker run --rm -it -p 8080:8080 clidey/whodb

Then open [http://localhost:8080](http://localhost:8080) and enter your database connection details.

Want to look around first? Try the [live demo](https://demo.whodb.com/) or watch the [video walkthrough](https://youtu.be/hnAQcYYzcLo).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 238 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. # <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/logo/logo.svg" width="30px" height="auto" alt="" /> WhoDB
  3. [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fclidey%2Fwhodb.svg)](https://mcptoplist.com/server/glama%2Fclidey%2Fwhodb)
  4. ### A lightweight, self-hosted workspace for your databases
  5. [![Release workflow](https://img.shields.io/github/actions/workflow/status/clidey/whodb/release-ce.yml?branch=main)](https://github.com/clidey/whodb/actions/workflows/release-ce.yml)
  6. [![Release version](https://img.shields.io/github/v/release/clidey/whodb)](https://github.com/clidey/whodb/releases)
  7. ![Release date](https://img.shields.io/github/release-date/clidey/whodb)
  8. ![Total downloads](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/clidey/whodb/main/badges/downloads.json)
  9. ![Docker size](https://img.shields.io/docker/image-size/clidey/whodb/latest)
  10. ![Commits per month](https://img.shields.io/github/commit-activity/m/clidey/whodb)
  11. ![Last commit](https://img.shields.io/github/last-commit/clidey/whodb)
  12. ![Contributors](https://img.shields.io/github/contributors/clidey/whodb)
  13. ![Closed issues](https://img.shields.io/github/issues-closed/clidey/whodb)
  14. ![Closed PRs](https://img.shields.io/github/issues-pr-closed/clidey/whodb)
  15. [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/clidey/whodb/blob/main/LICENSE)
  16. [![GitHub stars](https://img.shields.io/github/stars/clidey/whodb?style=social)](https://github.com/clidey/whodb/stargazers)
  17. ![Go](https://img.shields.io/badge/language-Go-00ADD8?logo=go&logoColor=white)
  18. ![TypeScript](https://img.shields.io/badge/language-TypeScript-3178c6?logo=typescript&logoColor=white)
  19. ## Available on
  20. [![Docker](https://img.shields.io/badge/Docker-available-brightgreen)](https://hub.docker.com/r/clidey/whodb)
  21. [![Windows](https://img.shields.io/badge/Windows-available-brightgreen)](https://apps.microsoft.com/detail/9pftx5bv4ds6)
  22. [![macOS](https://img.shields.io/badge/macOS-available-brightgreen)](https://apps.apple.com/app/whodb/id6754566536)
  23. [![Snap](https://img.shields.io/badge/Snap-available-brightgreen)](https://snapcraft.io/whodb)
  24. [![CLI](https://img.shields.io/badge/CLI-available-brightgreen)](https://github.com/clidey/whodb/blob/main/cli/README.md)
  25. [Quick start](https://github.com/clidey/whodb/blob/main/README.md#quick-start) · [Documentation](https://clidey.github.io/whodb/) · [Live demo](https://demo.whodb.com/) · [Community](https://github.com/clidey/whodb/discussions)
  26. </div>
  27. <p align="center">
  28. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/06-storage-unit-list-with-sidebar.png" alt="WhoDB showing a database table" width="100%" />
  29. </p>
  30. WhoDB gives you one place to explore your databases, edit data, run queries, and understand how a schema fits together. It runs in the browser, is easy to self-host, and is available as a desktop app or terminal CLI too.
  31. Use it when you want to inspect a local database, help a teammate explore unfamiliar data, or work without installing a heavyweight database client. AI features are optional: connect Ollama, OpenAI, Anthropic, LM Studio, or another OpenAI-compatible provider if you want to ask questions in plain English.
  32. ## Quick start
  33. Run WhoDB with Docker:
  34. ```bash
  35. docker run --rm -it -p 8080:8080 clidey/whodb
  36. ```
  37. Then open [http://localhost:8080](http://localhost:8080) and enter your database connection details.
  38. Want to look around first? Try the [live demo](https://demo.whodb.com/) or watch the [video walkthrough](https://youtu.be/hnAQcYYzcLo).
  39. ## What you can do
  40. - **Browse and edit data** in a spreadsheet-style grid with sorting, filtering, pagination, and inline editing.
  41. - **Understand a schema visually** with an interactive graph of tables and relationships.
  42. - **Work through queries in a scratchpad** with multiple cells, autocomplete, history, and results kept alongside each query.
  43. - **Move data in and out** with imports, exports, and mock-data generation for development and testing.
  44. - **Ask questions in plain English** using a local or hosted AI provider that you choose.
  45. - **Work from your terminal** through the WhoDB CLI and its MCP server.
  46. <table>
  47. <tr>
  48. <td width="50%">
  49. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/09-data-view-users-table.png" alt="Browsing rows in the WhoDB data grid" width="100%" />
  50. </td>
  51. <td width="50%">
  52. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/24-graph-view-schema-topology.png" alt="Exploring database relationships in the WhoDB schema graph" width="100%" />
  53. </td>
  54. </tr>
  55. <tr>
  56. <td align="center"><sub>Browse, filter, and edit data</sub></td>
  57. <td align="center"><sub>Follow relationships through the schema graph</sub></td>
  58. </tr>
  59. </table>
  60. ### Supported databases
  61. WhoDB Community supports:
  62. - PostgreSQL, CockroachDB, YugabyteDB, and QuestDB
  63. - MySQL, MariaDB, and TiDB
  64. - SQLite and DuckDB
  65. - MongoDB and FerretDB
  66. - Redis, Valkey, and Dragonfly
  67. - Elasticsearch and OpenSearch
  68. - ClickHouse and Memcached
  69. Support varies by database because not every system has the same concepts or capabilities. The connection screen shows the options available for each source.
  70. ## Installation options
  71. ### Docker with persistent sessions
  72. The one-line Docker command is ideal for trying WhoDB. To keep encrypted login sessions when the container is replaced, first generate a key and save it somewhere secure:
  73. ```bash
  74. openssl rand -hex 32
  75. ```
  76. Then mount `/data` and reuse that key whenever you start the container:
  77. ```bash
  78. docker run -it -p 8080:8080 \
  79. -v whodb-data:/data \
  80. -e WHODB_ENCRYPTION_KEY=your_saved_64_character_hex_key \
  81. clidey/whodb
  82. ```
  83. Keep that key somewhere safe. Changing it invalidates existing sessions. If WhoDB is served through an HTTPS reverse proxy, also set `WHODB_SECURE=true` so browsers only send the session cookie over HTTPS.
  84. See the [documentation](https://clidey.github.io/whodb/) for Docker Compose, connection profiles, SSL, AI providers, and other configuration options.
  85. ### Desktop
  86. - [macOS](https://apps.apple.com/app/whodb/id6754566536)
  87. - [Windows](https://apps.microsoft.com/detail/9pftx5bv4ds6)
  88. - [Snap](https://snapcraft.io/whodb)
  89. ### CLI and MCP server
  90. The CLI includes an interactive terminal UI and an MCP server for AI tools:
  91. ```bash
  92. # macOS and Linux
  93. curl -fsSL https://raw.githubusercontent.com/clidey/whodb/main/cli/install/install.sh | bash
  94. # or install with npm
  95. npm install -g @clidey/whodb
  96. ```
  97. ```bash
  98. whodb # open the terminal UI
  99. whodb mcp serve # start the MCP server
  100. ```
  101. See the [CLI guide](https://github.com/clidey/whodb/blob/main/cli/README.md) for connection examples and the full command reference.
  102. ## AI providers
  103. You can add a hosted AI provider directly from WhoDB—no backend configuration or restart is required. Open Chat, choose **Add Provider** from the provider menu, then select OpenAI, Anthropic, or Gemini and enter your API key. WhoDB will fetch the available models from that provider.
  104. Ollama and LM Studio are available as local options in WhoDB Community. By default, the backend looks for Ollama at `localhost:11434` and LM Studio at `localhost:1234/v1`, with local addresses adjusted automatically for Docker and WSL. Use `WHODB_OLLAMA_HOST`, `WHODB_OLLAMA_PORT`, or `WHODB_LMSTUDIO_BASE_URL` only when those defaults are not suitable for your setup.
  105. ### Optional backend provider configuration
  106. Environment variables let deployment administrators declare providers when the server starts. This is useful for preconfiguring OpenAI or Anthropic, changing provider endpoints, or adding an OpenAI-compatible service for everyone using that deployment:
  107. - `WHODB_OPENAI_*` for OpenAI
  108. - `WHODB_ANTHROPIC_*` for Anthropic
  109. - `WHODB_OLLAMA_*` for Ollama connection settings
  110. - `WHODB_LMSTUDIO_*` for LM Studio connection settings
  111. - `WHODB_AI_GENERIC_<ID>_*` for OpenAI-compatible providers
  112. See the [installation guide](https://clidey.github.io/whodb/installation#ai-providers) for the complete environment variable list and the [AI provider guide](https://clidey.github.io/whodb/ai/setup-providers) for setup examples.
  113. ## WhoDB Community and WhoDB Platform
  114. This repository contains **WhoDB Community**, the Apache-2.0-licensed database workspace described above. It is free to self-host and is the best place to start if you want to explore and work with databases.
  115. **WhoDB Platform** is the commercial, self-hosted edition for organizations that need shared projects, more data sources, SSO, fine-grained access controls, audit logs, pipelines, reporting, and internal apps. You can read the [WhoDB overview](https://whodb.com/) or compare plans on the [pricing page](https://whodb.com/pricing/).
  116. ## Development
  117. WhoDB has a Go backend and a React/TypeScript frontend. For local development, run them in separate terminals.
  118. Requirements:
  119. - Go
  120. - Node.js and pnpm
  121. Start the backend:
  122. ```bash
  123. cd core
  124. go run ./cmd/whodb
  125. ```
  126. Start the frontend:
  127. ```bash
  128. cd frontend
  129. pnpm install
  130. pnpm start
  131. ```
  132. The frontend opens at [http://localhost:3000](http://localhost:3000) and talks to the backend on port `8080`. See the [installation guide](https://github.com/clidey/whodb/blob/main/docs/installation.mdx#build-from-source) for generation and build commands.
  133. ## Contributing
  134. Bug reports, feature ideas, documentation improvements, and code contributions are all welcome.
  135. - [Open an issue](https://github.com/clidey/whodb/issues) for a bug or concrete request.
  136. - [Start a discussion](https://github.com/clidey/whodb/discussions) for questions and ideas.
  137. - Read [CONTRIBUTING.md](https://github.com/clidey/whodb/blob/main/CONTRIBUTING.md) before sending a pull request.
  138. ## More screenshots
  139. <details>
  140. <summary>See WhoDB in action</summary>
  141. ### Query scratchpad
  142. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/27-scratchpad-main-view.png" alt="Writing queries in the WhoDB scratchpad" width="100%" />
  143. ### Add and edit records
  144. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/11-data-view-add-row-dialog.png" alt="Adding a row in WhoDB" width="100%" />
  145. ### Build filters visually
  146. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/16-data-view-where-conditions-popover.png" alt="Building WHERE conditions in WhoDB" width="100%" />
  147. ### Export data
  148. <img src="https://raw.githubusercontent.com/clidey/whodb/main/docs/images/light/20-data-view-export-dialog.png" alt="Exporting data from WhoDB" width="100%" />
  149. </details>
  150. ## Support
  151. - [Documentation](https://clidey.github.io/whodb/)
  152. - [GitHub Issues](https://github.com/clidey/whodb/issues)
  153. - [support@clidey.com](mailto:support@clidey.com)
  154. WhoDB is licensed under the [Apache License 2.0](https://github.com/clidey/whodb/blob/main/LICENSE).
  155. <div align="center">
  156. If WhoDB saves you time, consider [giving the project a star](https://github.com/clidey/whodb/stargazers).
  157. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.