All 82 Dependencies
Every package WrenAI depends on, ranked by repo health score.
WrenAI (built by Canner) is an open-source GenBI (Generative BI) engine that gives AI agents a governed path from a plain-English question to trustworthy SQL, a chart, and a deployable dashboard. Rather than letting an LLM guess at your schema, WrenAI sits underneath the agent as a context layer: a version-controlled semantic model (MDL) that captures business definitions, approved joins, units, and examples, so every agent that touches the database inherits the same vetted understanding instead of re-learning it from scratch in a prompt.
The project is delivered as an agent-driven CLI (`pip install wrenai`) rather than a hosted app. Agents such as Claude Code, Cursor, or any MCP-capable client install a lightweight discovery stub (`npx skills add Canner/WrenAI`) that teaches them to pull workflow guides on demand — onboarding a warehouse, enriching business context, generating MDL, or building a GenBI app — so the guidance always matches the installed CLI version instead of drifting out of sync with static docs.
Under the hood, SQL planning and execution run through `wren-core`, a Rust engine built on Apache DataFusion that validates and rewrites queries against the MDL before they ever touch a warehouse (dry-plan validation, structured error codes, CTE rewriting). A WebAssembly build of that same engine, `wren-core-wasm`, lets deployed dashboards query static Parquet/DuckDB snapshots entirely client-side, so a generated GenBI app can be shipped to Vercel or Cloudflare Pages with zero backend.
WrenAI connects to 20+ data sources out of the box — BigQuery, Snowflake, PostgreSQL, MySQL, ClickHouse, Redshift, Databricks, Trino, Spark, and more — through a pluggable connector layer, and ships an MCP server so any MCP-aware agent can query through the same governed semantic layer instead of hitting the raw database directly.