All 37 Dependencies
Every package Docglow depends on, ranked by repo health score.
Docglow exists because thousands of teams run dbt Core without dbt Cloud, and the built-in `dbt docs generate && dbt docs serve` produces a documentation site that's functional but limited — no full-text search worth relying on, no health scoring, and a lineage view that doesn't scale well to large projects. Docglow generates a richer static documentation site from the same dbt project metadata.
It adds a lineage explorer for tracing model dependencies visually, health scoring to surface data quality or documentation gaps at a glance, and full-text search across models, columns, and descriptions — the kind of features teams would otherwise only get by paying for dbt Cloud.
MIT licensed and distributed as a PyPI package, Docglow generates a static site (a live demo is hosted separately), meaning the output can be deployed anywhere static files can be served, without depending on a running service.
