Evan Rusackas 56d1dae91e fix(docs): extend lint-docs-links to catch wrong-extension + missing-target
Previously the linter only flagged bare relative links (no .md/.mdx
extension). The Docusaurus build catches the other two classes
(`onBrokenMarkdownLinks: 'throw'`), but only after a multi-minute
compile. Now the source-level lint catches all three:

  bare              `[X](../foo)`            (skips file resolver entirely)
  missing-target    `[X](./gone.md)`         (target file doesn't exist)
  wrong-extension   `[X](./foo.md)` w/ .mdx  (the .md vs .mdx mismatch
                                              that broke the previous
                                              CI run on this branch)

Implementation:

- classifyLink() resolves the link target against the source file's
  directory. If it exists → ok. If not but the other extension does →
  wrong-extension (reports which extension is actually on disk). If
  neither exists → missing-target.
- Output groups findings by kind with category-specific explanations
  so the developer immediately knows whether to add an extension, fix
  one, or chase a real missing target.

Verified end-to-end by injecting one of each failure mode in turn
and confirming the linter reports the right file:line / category;
restoring the file always returns the lint to green.

Build-time `onBrokenMarkdownLinks: 'throw'` stays in place — defense
in depth. The lint just makes the same finding visible in seconds
rather than minutes.
2026-05-13 20:17:46 -07:00
2025-12-04 13:18:34 -05:00

Superset

License Latest Release on Github Build Status PyPI version PyPI GitHub Stars Contributors Last Commit Open Issues Open PRs Get on Slack Documentation

Superset logo (light)

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

superset-video-1080p.webm


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:

Amazon Athena   Amazon DynamoDB   Amazon Redshift   Apache Doris   Apache Drill   Apache Druid   Apache Hive   Apache Impala   Apache Kylin   Apache Pinot   Apache Solr   Apache Spark SQL   Ascend   Aurora MySQL (Data API)   Aurora PostgreSQL (Data API)   Azure Data Explorer   Azure Synapse   ClickHouse   Cloudflare D1   CockroachDB   Couchbase   CrateDB   Databend   Databricks   Denodo   Dremio   DuckDB   Elasticsearch   Exasol   Firebird   Firebolt   Google BigQuery   Google Sheets   Greenplum   Hologres   IBM Db2   IBM Netezza Performance Server   MariaDB   Microsoft SQL Server   MonetDB   MongoDB   MotherDuck   OceanBase   Oracle   Presto   RisingWave   SAP HANA   SAP Sybase   Shillelagh   SingleStore   Snowflake   SQLite   StarRocks   Superset meta database   TDengine   Teradata   TimescaleDB   Trino   Vertica   YDB   YugabyteDB

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

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

Understanding the Superset Points of View

Repo Activity

Performance Stats of apache/superset - Last 28 days
Languages
TypeScript 40.5%
Python 33.6%
Jupyter Notebook 22.5%
HTML 2.7%
JavaScript 0.4%
Other 0.2%