Reading the repo — stats and the shipped feed land in about ten seconds…
Business intelligence as code: build fast, interactive data visualizations in SQL and markdown
7.0k 427 17 openLast shipped 3d ago
Business intelligence as code: build fast, interactive data visualizations in SQL and markdown
Evidence improved chart rendering this week with better handling of irregular date ticks and pinned time-axis labels to prevent overlap. A new file attachment component shipped with organization-scoped private uploads. Behind the scenes, fixes landed across Snowflake timestamp handling, Postgres…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in evidence's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
fix(snowflake): render TIMESTAMP_TZ values in their stored offset instead of UTC (#2094)
fix(validators): narrow date validator to date_grain, drop stale date checks (#2140)
fix(postgres): run per-connection SETs on the awaited pool onConnect hook (#2138)
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.
