d60ce8c3ef
Resolves PR #39925 conflict against 68 master commits since the last rebase. Single conflict in `superset/models/dashboard.py::dashboard_link`: - HEAD (Slice 1, this branch): `url_for("Superset.dashboard", ...)` so Flask prepends SCRIPT_NAME and the row link works under subdirectory deployments. - master (#40404 area): `escape(self.url)` to defuse user-controlled slug HTML injection in the rendered FAB list-view anchor. Resolution combines both: keep `url_for` for the subdir-correct routing, wrap the result in `escape()` for HTML-attribute defence-in-depth. `url_for` already percent-encodes the slug path param (mitigating the XSS vector master targeted); the explicit `escape()` documents intent and survives any future change that adds query params/fragments. master also added `tests/unit_tests/models/dashboard_test.py` with two tests that instantiated `Dashboard` outside an application context. Adapted to use the `app_context` autouse fixture + a `current_app.test_request_context("/")` block so they exercise the `url_for`-based implementation. Semantic assertions preserved: the script-tag injection test still asserts no `<script>` or attribute breakout; the plain-slug test still asserts `/superset/dashboard/sales/` appears in the rendered href. All other touched files auto-merged cleanly (UPDATING.md, config.py, connectors/sqla/models.py, models/slice.py, views/utils.py, integration_tests/dashboards/api_tests.py, unit_tests/commands/report/execute_test.py). Notably slice.py's auto-merge correctly retained Slice 1's `slice_link` url_for refactor alongside master's new `icons` data-controlled HTML escape. SKIP=pylint applied for worktree-venv subshell baseline (pre-commit's pylint hook can't load the superset module without an activated venv; documented baseline across Slices 4-8). pylint verified independently against the changed files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Superset
A modern, enterprise-ready business intelligence web application.
Documentation
- User Guide — For analysts and business users. Explore data, build charts, create dashboards, and connect databases.
- Administrator Guide — Install, configure, and operate Superset. Covers security, scaling, and database drivers.
- Developer Guide — Contribute to Superset or build on its REST API and extension framework.
Why Superset? | Supported Databases | Release Notes | Get Involved | Resources | Organizations Using Superset
Why Superset?
Superset is a modern data exploration and data visualization platform. Superset can replace or augment proprietary business intelligence tools for many teams. Superset integrates well with a variety of data sources.
Superset provides:
- A no-code interface for building charts quickly
- A powerful, web-based SQL Editor for advanced querying
- A lightweight semantic layer for quickly defining custom dimensions and metrics
- Out of the box support for nearly any SQL database or data engine
- A wide array of beautiful visualizations to showcase your data, ranging from simple bar charts to geospatial visualizations
- Lightweight, configurable caching layer to help ease database load
- Highly extensible security roles and authentication options
- An API for programmatic customization
- A cloud-native architecture designed from the ground up for scale
Screenshots & Gifs
Video Overview
Large Gallery of Visualizations
Craft Beautiful, Dynamic Dashboards
No-Code Chart Builder
Powerful SQL Editor
Supported Databases
Superset can query data from any SQL-speaking datastore or data engine (Presto, Trino, Athena, and more) that has a Python DB-API driver and a SQLAlchemy dialect.
Here are some of the major database solutions that are supported:
A more comprehensive list of supported databases along with the configuration instructions can be found here.
Want to add support for your datastore or data engine? Read more here about the technical requirements.
Installation and Configuration
Try out Superset's quickstart guide or learn about the options for production deployments.
Get Involved
- Ask and answer questions on StackOverflow using the apache-superset tag
- Join our community's Slack and please read our Slack Community Guidelines
- Join our dev@superset.apache.org Mailing list. To join, simply send an email to dev-subscribe@superset.apache.org
- If you want to help troubleshoot GitHub Issues involving the numerous database drivers that Superset supports, please consider adding your name and the databases you have access to on the Superset Database Familiarity Rolodex
- Join Superset's Town Hall and Operational Model recurring meetings. Meeting info is available on the Superset Community Calendar
Contributor Guide
Interested in contributing? Check out our Developer Guide to find resources around contributing along with a detailed guide on how to set up a development environment.
Resources
- Superset "In the Wild" - see who's using Superset, and add your organization to the list!
- Feature Flags - the status of Superset's Feature Flags.
- Standard Roles - How RBAC permissions map to roles.
- Superset Wiki - Tons of additional community resources: best practices, community content and other information.
- Superset SIPs - The status of Superset's SIPs (Superset Improvement Proposals) for both consensus and implementation status.
Understanding the Superset Points of View
-
Getting Started with Superset
-
Deploying Superset
-
Recordings of Past Superset Community Events
-
Visualizations
Repo Activity
