6.9k stars · MIT · @evidence-dev/evidence@40.1.8 (2026-02-06) · Track this in Rising ↗
Business intelligence as Markdown files with SQL in them, building to a static site — a dashboard Claude Code can write.
Radar check
What we found when we opened it. Every bar is one fact, with its date.
Last code pushed 23 Oct 2026, 4 days before this check.
Latest release @evidence-dev/evidence@40.1.8 on 6 Feb 2026.
Public since May 2021, a little over 5 years.
7,060 stars and 430 forks.
100 commits and 10 new issues in the last 90 days.
76 contributors. No pull requests merged in 90 days; changes go in directly.
No security policy file says how to report a problem. No published security advisories.
How the bars are scored
- Alive. Days since the last code push: a week or less 100, a month 90, three months 70, six months 50, a year 30, eighteen months 15, older 0.
- Releases. Age of the latest GitHub release, on a similar scale; no bar when the project publishes no releases.
- Maturity. Age of the project: eight years 100, five 90, three 70, two 55, one 40, six months 25, younger 10.
- Adoption. Stars on a log scale: 100,000 stars is 100, 10,000 is 80, 1,000 is 60, 100 is 40.
- Activity. Commits in the last 90 days: 300 or more 100, 100 85, 30 65, 10 45, any 25.
- Community. People who have contributed: 100 or more 100, 30 80, 10 60, 5 40, 2 25, one 10.
- Security. A published security policy 80, none 40; published advisories are listed, not scored.
Checked by Repo Radar on 26 Oct 2026 from the repository on GitHub. Covered in Edition 8.
▶Repo detailsthe review · specs · pros & cons · install
What it does
Each page is a Markdown file. You write a SQL query inside it, give the result a name, and drop in a chart component that reads that name. The build runs the queries, renders the pages, and writes a static website. It connects to PostgreSQL, MySQL, SQLite, DuckDB, CSV files and several warehouses. Charts, tables, filters and value formatting are built in. The whole project is text in a repository, so changes are reviewed as code and an assistant can write a page the same way it writes application code. The npm release is 40.1.8 from February 2026, and code was last pushed on 24 September 2026, so the project is active even though releases are infrequent. It queries at build time, so it does not show live data.
Why it matters
Who it suits. A small team whose numbers are spread across several databases and who want one page that joins them. It suits people who already work in a code repository and dislike dragging widgets around a builder. Skip it if the data has to update every few seconds, because a scheduled rebuild is the only refresh available.
Verdict. The right shape of reporting tool for a text-first workflow, and the wrong one for anybody who wants to click. Be honest about timing: it is premature until something is actually producing numbers, so read this now and install it after entry 4 has been running for a few weeks. The build toolchain is a real ongoing cost. Metabase is the better answer when non-technical people need to build their own charts, and Superset when the organisation is larger.
Summary (Key Points)from the README
Key features
- SQL and Markdown reports: You write reports in code, combining SQL queries with Markdown text.
- Built-in Agent: You can develop reports with Evidence's Agent instead of working locally.
- Local AI coding tools: You can develop on your own machine with tools such as Claude Code or Cursor.
- Self-hosting: You can host the generated static site on your own infrastructure.
- Evidence Studio publishing: You can publish a project on Evidence Studio for hosted reports.
- Open source under MIT: The code is licensed under the MIT license, with the license text in the repository's LICENSE file.
- Community support: A Slack channel is available for discussion, sharing work and asking for help.
- Documented contribution process: CONTRIBUTING.md explains how pull requests are reviewed and merged.
Ways to install
| Platform or method | What it needs | Effort |
|---|---|---|
| macOS / Linux | Not specified in the README | Not specified in the README |
| Windows | Not specified in the README | Not specified in the README |
Important
- Install commands not shown: The README lists macOS/Linux and Windows install sections, but the commands themselves are not included in the text provided, so check the docs for exact steps.
- Hosting choice: Hosted publishing goes through Evidence Studio, while self-hosting means you run the generated static site on your own infrastructure. The README does not describe pricing or infrastructure requirements; see the publishing docs.
- Third-party tools: The local workflow mentions Claude Code and Cursor, which are separate products that the README does not describe or cover.
Written by an AI model from the project’s README; not part of the review, and it can be wrong.
- Everything is text in version control. Changes are reviewed, and nothing is trapped in a builder.
- The output is a static site, so there is little to keep running and little to secure.
- It talks to PostgreSQL, SQLite and DuckDB natively, which covers most small setups.
- A Node build toolchain is a second ecosystem to keep working, and version drift costs time.
- Queries run at build time, so a live view means a scheduled rebuild.
- Releases are infrequent even though code lands regularly, which makes the project look quieter than it is.
# needs Node 18 or newer npx degit evidence-dev/template my-dashboard cd my-dashboard npm install npm run sources npm run dev
