duckcheck 0.4.0__tar.gz

duckcheck-0.4.0/.github/workflows/ci.yml

@@ -0,0 +1,11 @@
+name: CI
+on: [push, pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: {python-version: "3.12"}
+      - run: pip install -e ".[dev]"
+      - run: pytest tests/ -v

duckcheck-0.4.0/.gitignore

@@ -0,0 +1,5 @@
+__pycache__/
+.venv/
+.pytest_cache/
+.duckcheck/
+dist/

duckcheck-0.4.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog
+
+## [0.4.0] - 2026-09-14
+
+### Added
+- `custom_sql` `expect` operators: `0`, `=N`, `>N`, `<N`, `>=N`, `<=N` (default `0`)
+- `duckcheck run --format json` for machine-readable CI output
+
+## [0.3.0] - 2026-08-19
+
+### Added
+- SQLite sources (`sqlite://path` or `.db`) via DuckDB ATTACH
+- `row_count_delta` checks with `duckcheck baseline update`
+- `DUCKCHECK_NOW` to freeze freshness comparisons in tests/CI
+
+## [0.2.0] - 2026-08-19
+
+### Added
+- Check types: `custom_sql`, `freshness`, `row_count`
+- `--junit` XML output and `--source-table` override
+- `${ENV}` substitution in source URIs; suite-relative CSV/Parquet paths
+- Postgres/MySQL ATTACH stubs (not integration-tested against a live DB)
+
+## [0.1.0] - 2026-08-18
+
+### Added
+- DuckDB-powered not_null, unique, accepted_values checks
+- YAML suite format and CLI

duckcheck-0.4.0/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing
+
+## Running tests
+
+Prefer Docker Compose:
+
+```bash
+docker compose run --rm test
+docker compose run --rm run-example
+```
+
+Locally:
+
+```bash
+pip install -e ".[dev]"
+pytest tests/ -v
+duckcheck run examples/clean.yaml
+```
+
+## Pull requests
+
+- Keep example suites intentional (`clean.yaml` passes; `checks.yaml` may fail on purpose)
+- Update README/CHANGELOG for new check types or CLI flags
+- Prefer small PRs with a clear test plan
+
+## Commit style
+
+- Imperative subject line; mention the user-facing why when relevant
+- Do not add AI co-author trailers (e.g. Co-authored-by: Cursor) to commits.

duckcheck-0.4.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 duckcheck contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

duckcheck-0.4.0/PKG-INFO

@@ -0,0 +1,145 @@
+Metadata-Version: 2.5
+Name: duckcheck
+Version: 0.4.0
+Summary: Lightweight data quality checks powered by DuckDB
+Project-URL: Homepage, https://github.com/yashshah9/duckcheck
+Project-URL: Repository, https://github.com/yashshah9/duckcheck
+Project-URL: Issues, https://github.com/yashshah9/duckcheck/issues
+Author-email: Yash Shah <yash376351@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: click>=8.1
+Requires-Dist: duckdb>=1.0
+Requires-Dist: pydantic>=2.6
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.7
+Requires-Dist: structlog>=24.1
+Provides-Extra: dev
+Requires-Dist: mypy>=1.9; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.4; extra == 'dev'
+Requires-Dist: types-pyyaml>=6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# duckcheck
+
+Lightweight data quality checks powered by **DuckDB** — the anti–Great Expectations for teams who want `pip install`, one YAML file, and one command.
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
+[![CI](https://github.com/yashshah9/duckcheck/actions/workflows/ci.yml/badge.svg)](https://github.com/yashshah9/duckcheck/actions/workflows/ci.yml)
+
+> **Status:** v0.4 — CSV/Parquet/SQLite sources, custom SQL with `expect` operators, freshness, baselines, JUnit, and `--format json`.
+
+## 60-second try
+
+```bash
+docker compose run --rm run-example  # duckcheck run examples/clean.yaml
+docker compose run --rm test         # pytest
+```
+
+## Why this vs alternatives
+
+| Approach | Strength | Gap |
+|----------|----------|-----|
+| **duckcheck** | One YAML + DuckDB, local files, CI-friendly | Not a full observability platform |
+| Great Expectations | Rich ecosystem | Heavyweight setup for simple column checks |
+| Soda Core | Familiar check DSL | Cloud-oriented workflow |
+| Ad-hoc SQL in CI | Zero new tools | No standard report / JUnit / baselines |
+
+## Problem
+
+Data teams need to assert column quality in CI, but Great Expectations is heavyweight and Soda Core funnels to cloud. Ad-hoc SQL checks have no reporting standard.
+
+## Key features (v0.4)
+
+- YAML check definitions
+- DuckDB scans CSV, Parquet, and SQLite locally — no server
+- Checks: `not_null`, `unique`, `accepted_values`, `custom_sql`, `freshness`, `row_count`, `row_count_delta`
+- `custom_sql` `expect` operators: `0`, `=N`, `>N`, `<N`, `>=N`, `<=N` (default `0`)
+- `--format json` and `--junit` for CI dashboards
+- `${ENV}` in source URIs; `--source-table` for SQL ATTACH
+
+## Architecture
+
+```
+duckcheck run checks.yaml
+    └── SuiteSpec (Pydantic)
+            └── DuckDB in-process
+                    └── source_data view from CSV/Parquet
+```
+
+| Component | Technology | Why |
+|-----------|------------|-----|
+| Engine | DuckDB | Single dependency, scans files + SQL databases |
+| CLI | Click + Rich | Simple, good terminal UX |
+| Spec | YAML + Pydantic | Version-controllable checks |
+
+## Installation
+
+```bash
+pip install duckcheck
+pip install -e ".[dev]"
+```
+
+## Usage
+
+```bash
+duckcheck health
+duckcheck run examples/clean.yaml
+duckcheck run examples/checks.yaml   # fixture with known failures
+duckcheck run examples/clean.yaml --junit /tmp/duckcheck.xml
+duckcheck run examples/clean.yaml --format json
+duckcheck baseline update examples/clean.yaml
+```
+
+Example `checks.yaml`:
+
+```yaml
+name: sample-suite
+source: examples/sample.csv
+checks:
+  - name: id_not_null
+    type: not_null
+    column: id
+  - name: status_values
+    type: accepted_values
+    column: status
+    values: [active, inactive]
+  - name: three_active
+    type: custom_sql
+    sql: "SELECT * FROM source_data WHERE status = 'active'"
+    expect: "=3"
+```
+
+## Docker
+
+```bash
+docker compose run --rm test
+docker compose run --rm run-example
+```
+
+## Running tests
+
+```bash
+pytest tests/ -v
+```
+
+## Roadmap
+
+- [x] Freshness + row_count + custom_sql + JUnit
+- [x] Row-count baseline delta store (`duckcheck baseline update`)
+- [x] custom_sql `expect` operators + `--format json`
+- [ ] Live Postgres/MySQL ATTACH integration tests
+- [ ] Airflow/Dagster operators
+
+## License
+
+MIT
+
+## Known limitations (v0.4)
+
+- Postgres/MySQL ATTACH is stubbed (`INSTALL/LOAD`) — no live DB in CI yet
+- `examples/checks.yaml` is a failing fixture; `examples/clean.yaml` is the happy path
+- Checks still run against a `source_data` view

duckcheck-0.4.0/README.md

@@ -0,0 +1,121 @@
+# duckcheck
+
+Lightweight data quality checks powered by **DuckDB** — the anti–Great Expectations for teams who want `pip install`, one YAML file, and one command.
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
+[![CI](https://github.com/yashshah9/duckcheck/actions/workflows/ci.yml/badge.svg)](https://github.com/yashshah9/duckcheck/actions/workflows/ci.yml)
+
+> **Status:** v0.4 — CSV/Parquet/SQLite sources, custom SQL with `expect` operators, freshness, baselines, JUnit, and `--format json`.
+
+## 60-second try
+
+```bash
+docker compose run --rm run-example  # duckcheck run examples/clean.yaml
+docker compose run --rm test         # pytest
+```
+
+## Why this vs alternatives
+
+| Approach | Strength | Gap |
+|----------|----------|-----|
+| **duckcheck** | One YAML + DuckDB, local files, CI-friendly | Not a full observability platform |
+| Great Expectations | Rich ecosystem | Heavyweight setup for simple column checks |
+| Soda Core | Familiar check DSL | Cloud-oriented workflow |
+| Ad-hoc SQL in CI | Zero new tools | No standard report / JUnit / baselines |
+
+## Problem
+
+Data teams need to assert column quality in CI, but Great Expectations is heavyweight and Soda Core funnels to cloud. Ad-hoc SQL checks have no reporting standard.
+
+## Key features (v0.4)
+
+- YAML check definitions
+- DuckDB scans CSV, Parquet, and SQLite locally — no server
+- Checks: `not_null`, `unique`, `accepted_values`, `custom_sql`, `freshness`, `row_count`, `row_count_delta`
+- `custom_sql` `expect` operators: `0`, `=N`, `>N`, `<N`, `>=N`, `<=N` (default `0`)
+- `--format json` and `--junit` for CI dashboards
+- `${ENV}` in source URIs; `--source-table` for SQL ATTACH
+
+## Architecture
+
+```
+duckcheck run checks.yaml
+    └── SuiteSpec (Pydantic)
+            └── DuckDB in-process
+                    └── source_data view from CSV/Parquet
+```
+
+| Component | Technology | Why |
+|-----------|------------|-----|
+| Engine | DuckDB | Single dependency, scans files + SQL databases |
+| CLI | Click + Rich | Simple, good terminal UX |
+| Spec | YAML + Pydantic | Version-controllable checks |
+
+## Installation
+
+```bash
+pip install duckcheck
+pip install -e ".[dev]"
+```
+
+## Usage
+
+```bash
+duckcheck health
+duckcheck run examples/clean.yaml
+duckcheck run examples/checks.yaml   # fixture with known failures
+duckcheck run examples/clean.yaml --junit /tmp/duckcheck.xml
+duckcheck run examples/clean.yaml --format json
+duckcheck baseline update examples/clean.yaml
+```
+
+Example `checks.yaml`:
+
+```yaml
+name: sample-suite
+source: examples/sample.csv
+checks:
+  - name: id_not_null
+    type: not_null
+    column: id
+  - name: status_values
+    type: accepted_values
+    column: status
+    values: [active, inactive]
+  - name: three_active
+    type: custom_sql
+    sql: "SELECT * FROM source_data WHERE status = 'active'"
+    expect: "=3"
+```
+
+## Docker
+
+```bash
+docker compose run --rm test
+docker compose run --rm run-example
+```
+
+## Running tests
+
+```bash
+pytest tests/ -v
+```
+
+## Roadmap
+
+- [x] Freshness + row_count + custom_sql + JUnit
+- [x] Row-count baseline delta store (`duckcheck baseline update`)
+- [x] custom_sql `expect` operators + `--format json`
+- [ ] Live Postgres/MySQL ATTACH integration tests
+- [ ] Airflow/Dagster operators
+
+## License
+
+MIT
+
+## Known limitations (v0.4)
+
+- Postgres/MySQL ATTACH is stubbed (`INSTALL/LOAD`) — no live DB in CI yet
+- `examples/checks.yaml` is a failing fixture; `examples/clean.yaml` is the happy path
+- Checks still run against a `source_data` view

duckcheck-0.4.0/SECURITY.md

@@ -0,0 +1,14 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Email **yash376351@gmail.com** with the repo name, a short description, and steps to reproduce. Please do not open a public issue for exploitable findings until we have had a reasonable chance to respond.
+
+## Threat model (honest)
+
+duckcheck runs SQL checks locally via DuckDB against files or attached databases you point it at.
+
+- Custom SQL is executed as written — only load suites and sources you trust.
+- `${ENV}` substitution can pull secrets into URIs; prefer non-secret paths in committed YAML.
+- duckcheck is a **data quality runner**, not an access-control layer for your warehouse.
+- Postgres/MySQL ATTACH helpers are stubs today; do not assume network DB hardening from this tool.

duckcheck-0.4.0/compose.yaml

@@ -0,0 +1,11 @@
+services:
+  test:
+    build: {context: ., dockerfile: docker/Dockerfile}
+    volumes: [".:/app"]
+    working_dir: /app
+    command: ["pytest", "tests/", "-v"]
+  run-example:
+    build: {context: ., dockerfile: docker/Dockerfile}
+    volumes: [".:/app"]
+    working_dir: /app
+    command: ["duckcheck", "run", "examples/clean.yaml"]

duckcheck-0.4.0/docker/Dockerfile

@@ -0,0 +1,8 @@
+FROM python:3.12-slim AS dev
+WORKDIR /app
+COPY pyproject.toml README.md ./
+COPY src ./src
+COPY examples ./examples
+COPY tests ./tests
+RUN pip install --no-cache-dir -e ".[dev]"
+CMD ["pytest", "tests/", "-v"]

duckcheck-0.4.0/examples/checks.yaml

@@ -0,0 +1,22 @@
+name: sample-suite
+source: sample.csv
+checks:
+  - name: id_not_null
+    type: not_null
+    table: source_data
+    column: id
+  - name: name_not_null
+    type: not_null
+    table: source_data
+    column: name
+  - name: status_values
+    type: accepted_values
+    table: source_data
+    column: status
+    values: [active, inactive]
+  - name: at_least_one_row
+    type: row_count
+    min_rows: 1
+  - name: no_negative_amounts
+    type: custom_sql
+    sql: SELECT * FROM source_data WHERE amount < 0

duckcheck-0.4.0/examples/clean.csv

@@ -0,0 +1,4 @@
+id,name,status,amount,updated_at
+1,Alice,active,100,2099-01-01 00:00:00
+2,Bob,inactive,200,2099-01-01 00:00:00
+3,Charlie,active,50,2099-01-01 00:00:00

duckcheck-0.4.0/examples/clean.yaml

@@ -0,0 +1,19 @@
+name: clean-suite
+source: clean.csv
+checks:
+  - name: id_not_null
+    type: not_null
+    column: id
+  - name: name_not_null
+    type: not_null
+    column: name
+  - name: status_values
+    type: accepted_values
+    column: status
+    values: [active, inactive]
+  - name: at_least_one_row
+    type: row_count
+    min_rows: 1
+  - name: no_negative_amounts
+    type: custom_sql
+    sql: SELECT * FROM source_data WHERE amount < 0

duckcheck-0.4.0/examples/sample.csv

@@ -0,0 +1,5 @@
+id,name,status,amount,updated_at
+1,Alice,active,100,2099-01-01 00:00:00
+2,Bob,active,200,2099-01-01 00:00:00
+3,,active,50,2099-01-01 00:00:00
+4,Charlie,invalid,300,2099-01-01 00:00:00

duckcheck-0.4.0/plans/README.md

@@ -0,0 +1,6 @@
+# duckcheck — Planning Documents
+
+| Document | Status | Description |
+|----------|--------|-------------|
+| [v0.1-completed-foundation.md](./v0.1-completed-foundation.md) | **Completed** | Initial foundation release |
+| [v0.2-next-phase-roadmap.md](./v0.2-next-phase-roadmap.md) | **In Progress** | v0.2.0 shipped extra checks + JUnit; live ATTACH still open |

duckcheck-0.4.0/plans/v0.1-completed-foundation.md

@@ -0,0 +1,200 @@
+# v0.1 Completed Foundation Plan — duckcheck
+
+**Status:** Completed  
+**Version:** 0.1.0  
+**Completed:** 2026-08-18  
+**Owner:** Yash Shah  
+
+---
+
+## 1. Executive Summary
+
+Deliver a **minimal viable open-source foundation** for lightweight data quality checks powered by DuckDB. v0.1 focuses on YAML-defined column checks (`not_null`, `unique`, `accepted_values`) against local CSV/Parquet files — zero server infrastructure, CI-ready from day one via exit codes and Docker.
+
+---
+
+## 2. Problem Statement
+
+- Data teams need column-level quality assertions in CI, but Great Expectations is heavyweight and Soda Core funnels toward cloud
+- Ad-hoc SQL checks have no standard reporting format or reusable spec
+- DuckDB can scan files in-process, but no thin CLI wraps it for check suites
+- Teams want `pip install`, one YAML file, one command — not a platform
+
+---
+
+## 3. Goals (v0.1)
+
+| # | Goal | Status |
+|---|------|--------|
+| G1 | Provide CLI installable Python package | Done |
+| G2 | YAML check suite definitions with Pydantic validation | Done |
+| G3 | Three core check types: `not_null`, `unique`, `accepted_values` | Done |
+| G4 | CSV (and Parquet) source via DuckDB in-process | Done |
+| G5 | Click + Rich CLI with pass/fail exit codes | Done |
+| G6 | Docker-based dev and test environment | Done |
+| G7 | Contributor-ready repo (README, CI, LICENSE) | Done |
+
+## 4. Non-Goals (v0.1)
+
+- Postgres/MySQL via DuckDB ATTACH
+- Freshness or row-count delta checks
+- JUnit XML or other CI report formats
+- Custom SQL check type
+- Airflow/Dagster operators
+- PyPI publish (deferred to v0.2)
+- Web UI or hosted dashboard
+- Great Expectations compatibility layer
+
+---
+
+## 5. Architecture Delivered
+
+```
+CLI (Click + Rich)
+  ├── health        → version + sanity check
+  └── run <suite>   → runner.py → DuckDB in-process
+
+Models (Pydantic v2)
+  ├── SuiteSpec     → name, source path, checks[]
+  └── CheckSpec     → name, type, table, column, values[]
+
+Engine (DuckDB)
+  ├── _register_source()  → CREATE VIEW source_data
+  └── _run_check()        → SQL per check type
+
+Infrastructure
+  ├── structlog logging
+  └── Docker Compose (test, run-example)
+```
+
+### Data Flow
+
+```
+checks.yaml
+    └── SuiteSpec.model_validate()
+            └── duckdb.connect()
+                    ├── read_csv_auto(source) → VIEW source_data
+                    └── per-check SQL → CheckResult[]
+                            └── RunReport → Rich table → exit 0|1
+```
+
+### Technology Choices
+
+| Layer | Choice | Rationale |
+|-------|--------|-----------|
+| Engine | DuckDB ≥1.0 | Single dependency; scans CSV/Parquet locally; future ATTACH for SQL DBs |
+| Language | Python 3.11+ | Data team familiarity, pytest integration |
+| CLI | Click | Mature, composable subcommands |
+| Terminal UX | Rich | Colored pass/fail tables, readable CI output |
+| Validation | Pydantic v2 | Strict YAML schemas, actionable validation errors |
+| Logging | structlog | Structured JSON-capable logs per check |
+| Packaging | hatchling | Modern pyproject.toml builds |
+| Quality | ruff, mypy, pytest | Standard Python OSS toolchain |
+
+---
+
+## 6. Deliverables Completed
+
+### 6.1 Source Code
+
+- [x] `src/duckcheck/cli.py` — `health`, `run` commands with Rich table output
+- [x] `src/duckcheck/runner.py` — DuckDB connection, source registration, check execution
+- [x] `src/duckcheck/spec.py` — `SuiteSpec`, `CheckSpec` Pydantic models
+- [x] `src/duckcheck/__init__.py` — package version
+
+### 6.2 Check Types Implemented
+
+| Check Type | SQL Strategy | Pass Condition |
+|------------|--------------|----------------|
+| `not_null` | `COUNT(*) WHERE col IS NULL` | Count = 0 |
+| `unique` | `COUNT(*) - COUNT(DISTINCT col)` | Duplicates = 0 |
+| `accepted_values` | `COUNT(*) WHERE col NOT IN (...)` | Invalid rows = 0 |
+
+### 6.3 Source Formats Supported
+
+| Format | DuckDB Function | Status |
+|--------|-----------------|--------|
+| CSV | `read_csv_auto(path)` | Done |
+| Parquet | `read_parquet(path)` | Done |
+| Postgres/MySQL | ATTACH | Deferred v0.2 |
+
+### 6.4 Examples & Fixtures
+
+- [x] `examples/checks.yaml` — sample suite with intentional failure (`name_not_null`)
+- [x] `examples/sample.csv` — test dataset with null name row
+
+### 6.5 Tests
+
+- [x] `tests/test_runner.py` — suite execution, failure detection on null column
+- [x] All tests passing in Docker (Python 3.12)
+
+### 6.6 DevOps & Documentation
+
+- [x] `docker/Dockerfile` — multi-stage dev/runtime
+- [x] `compose.yaml` — `test` and `run-example` services
+- [x] `.github/workflows/ci.yml` — ruff, mypy, pytest
+- [x] `README.md`, `CHANGELOG.md`, `LICENSE`
+- [x] `pyproject.toml` — hatchling build, `[project.scripts]` entry point
+
+---
+
+## 7. YAML Spec Schema (v0.1)
+
+```yaml
+name: sample-suite          # required — suite identifier
+source: examples/sample.csv # required — path to CSV or Parquet
+checks:
+  - name: id_not_null       # required — unique check name
+    type: not_null          # required — not_null | unique | accepted_values
+    table: source_data      # required — view name (always source_data in v0.1)
+    column: id              # required for column checks
+  - name: status_values
+    type: accepted_values
+    table: source_data
+    column: status
+    values: [active, inactive]  # required for accepted_values
+```
+
+---
+
+## 8. Acceptance Criteria (Met)
+
+| # | Criterion | Verification |
+|---|-----------|--------------|
+| AC1 | `duckcheck run examples/checks.yaml` exits non-zero on failure | Manual + Docker `run-example` |
+| AC2 | Rich table shows PASS/FAIL per check with message | Manual |
+| AC3 | `docker compose run --rm test` passes all tests | CI-ready |
+| AC4 | Package installable via `pip install -e .` on Python 3.11+ | pyproject.toml |
+| AC5 | CSV source registered as `source_data` view | runner.py unit test |
+| AC6 | Unknown check type returns FAIL with descriptive message | runner.py |
+| AC7 | No secrets or credentials in repository | .gitignore, no .env committed |
+
+---
+
+## 9. Known Limitations (v0.1)
+
+- Single source per suite — no multi-table joins
+- `table` field in YAML is informational; all checks query `source_data` view
+- No parameterized connection strings for remote databases
+- No JUnit XML — CI must parse stdout or rely on exit code only
+- Column names interpolated into SQL without quoting (safe for simple identifiers only)
+- Parquet supported in code but not covered by example fixtures
+
+---
+
+## 10. Metrics at Completion
+
+| Metric | Value |
+|--------|-------|
+| Source files | 4 Python modules |
+| Test cases | 1 (integration-style) |
+| CLI commands | 2 (`health`, `run`) |
+| Check types | 3 |
+| Source formats | 2 (CSV, Parquet) |
+| Docker services | 2 (`test`, `run-example`) |
+
+---
+
+## 11. Sign-Off
+
+v0.1 foundation is **complete and shippable** as an alpha OSS project. The DuckDB + YAML + Rich CLI stack provides immediate value for local CSV/Parquet quality gates without server infrastructure. Database ATTACH, freshness checks, JUnit output, and orchestrator integration are deferred to v0.2 per roadmap.