dataenginex 0.4.3__tar.gz → 0.4.4__tar.gz

{dataenginex-0.4.3 → dataenginex-0.4.4}/.claude/commands/new-feature.md

@@ -1,4 +1,4 @@
-# New Feature (DEX)
+# New Feature (DataEngineX)
 
 Scaffold a new feature for the `dataenginex` core framework. Ask for the feature name and description if not provided as $ARGUMENTS.
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/.claude/commands/validate.md

@@ -1,6 +1,6 @@
-# Validate (DEX)
+# Validate (DataEngineX)
 
-Run the full DEX validation pipeline in order. Stop and report on first failure.
+Run the full DataEngineX validation pipeline in order. Stop and report on first failure.
 
 1. **Lint**
 
@@ -25,10 +25,11 @@ Run the full DEX validation pipeline in order. Stop and report on first failure.
    ```bash
    uv run python examples/02_api_quickstart.py &
    sleep 2
-   curl -sf http://localhost:17000/health   | python -m json.tool
-   curl -sf http://localhost:17000/         | python -m json.tool
-   curl -sf http://localhost:17000/metrics  | head -20
-   curl -sf -X POST http://localhost:17000/echo -H "Content-Type: application/json" -d '{"message":"test"}' | python -m json.tool
+   # dataenginex has no built-in HTTP server; these endpoints apply to dex-studio
+   curl -sf http://localhost:7860/health   | python -m json.tool
+   curl -sf http://localhost:7860/         | python -m json.tool
+   curl -sf http://localhost:7860/metrics  | head -20
+   curl -sf -X POST http://localhost:7860/echo -H "Content-Type: application/json" -d '{"message":"test"}' | python -m json.tool
    ```
 
    Check response **bodies** — not just status codes. Kill the server after.

{dataenginex-0.4.3 → dataenginex-0.4.4}/.github/dependabot.yml

@@ -4,9 +4,7 @@ updates:
     directory: "/"
     schedule:
       interval: weekly
-    target-branch: dev
   - package-ecosystem: github-actions
     directory: "/"
     schedule:
       interval: weekly
-    target-branch: dev

{dataenginex-0.4.3 → dataenginex-0.4.4}/.github/release-pr-template.md

@@ -1,6 +1,6 @@
 # Release PR Template
 
-Use this template whenever opening a release PR (`dev → main`). Reference `release-notes.md` and verify QA steps before merging.
+Use this template whenever opening a release PR to `main`. Reference `release-notes.md` and verify QA steps before merging.
 
 ## Summary
 

dataenginex-0.4.4/.github/workflows/auto-pr.yml

@@ -0,0 +1,16 @@
+name: Auto PR
+
+on:
+  push:
+    branches:
+      - '*'
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  auto-pr:
+    if: github.ref_name != 'main'
+    uses: TheDataEngineX/.github/.github/workflows/reusable-auto-pr-to-main.yml@main
+    secrets: inherit

{dataenginex-0.4.3 → dataenginex-0.4.4}/.github/workflows/ci.yml

@@ -2,9 +2,9 @@ name: CI
 
 on:
   push:
-    branches: [main, dev]
+    branches: [main]
   pull_request:
-    branches: [main, dev]
+    branches: [main]
   workflow_dispatch:
 
   schedule:
@@ -27,8 +27,12 @@ jobs:
       - run: uv sync --group ml
         env:
           UV_PROJECT_ENVIRONMENT: .venv
+      - uses: reviewdog/action-actionlint@v1
+
       - run: uv run poe quality
 
+      - run: uv build
+
   test:
     name: Tests (Python 3.13)
     runs-on: ubuntu-latest

{dataenginex-0.4.3 → dataenginex-0.4.4}/.github/workflows/release.yml

@@ -80,6 +80,6 @@ jobs:
           RELEASE_TAG: ${{ inputs.tag || github.ref_name }}
         run: |
           gh release create "$RELEASE_TAG" \
-            --title "DEX $RELEASE_TAG" \
+            --title "dataenginex $RELEASE_TAG" \
             --generate-notes \
             "sbom-dex-${{ steps.version.outputs.version }}.json"

{dataenginex-0.4.3 → dataenginex-0.4.4}/.github/workflows/security.yml

@@ -2,9 +2,9 @@ name: Security Scans
 
 on:
   push:
-    branches: [main, dev]
+    branches: [main]
   pull_request:
-    branches: [main, dev]
+    branches: [main]
   workflow_dispatch:
 
 permissions:
@@ -13,5 +13,5 @@ permissions:
 
 jobs:
   security:
-    uses: TheDataEngineX/.github/.github/workflows/security.yml@main
+    uses: TheDataEngineX/.github/.github/workflows/reusable-security.yml@main
     secrets: inherit

{dataenginex-0.4.3 → dataenginex-0.4.4}/CLAUDE.md

@@ -1,4 +1,4 @@
-# CLAUDE.md — DEX (dataenginex)
+# CLAUDE.md — DataEngineX (dataenginex)
 
 Brief answers only. No explanations unless asked.
 Goal is to save Claude code tokens for lower cost without losing quality.
@@ -7,7 +7,7 @@ Goal is to save Claude code tokens for lower cost without losing quality.
 
 ## Project Overview
 
-**DEX** — unified Data + ML + AI library. Config-driven, self-hosted, local-first. Pure Python — no bundled HTTP server.
+**DataEngineX** — unified Data + ML + AI library. Config-driven, self-hosted, local-first. Pure Python — no bundled HTTP server.
 
 | Package | Location | Purpose |
 |---------|----------|---------|
@@ -41,7 +41,7 @@ dex validate dex.yaml     # Validate config file
 dex version               # Show version + environment
 
 # Dev
-uv run poe dev            # Dev server (uvicorn reload, port 17000) — for examples/API testing only
+uv run poe dev            # Dev server (uvicorn reload, port 17000) — for examples/API testing only (dataenginex has no built-in HTTP server; see dex-studio for web UI)
 uv run poe docker-up      # Docker compose up
 uv run poe docker-down    # Docker compose down
 
@@ -63,7 +63,7 @@ pip install 'litellm>=1.83.3' --no-deps # LLM routing (separate: pins python-dot
 
 ______________________________________________________________________
 
-## Mandatory Validation
+## Validation
 
-Run `/validate` after ANY code change. Steps 4-5 (config validation + server smoke test) are NON-NEGOTIABLE.
-Tests passing ≠ app working.
+After any code change run: `uv run poe check-all` (lint + typecheck + test).
+Tests passing ≠ app working — run `dex validate dex.yaml` to verify config.

{dataenginex-0.4.3 → dataenginex-0.4.4}/CONTRIBUTING.md

@@ -1,18 +1,18 @@
-# Contributing to DEX
+# Contributing to DataEngineX
 
 Thank you for your interest in contributing to DataEngineX!
 
-**→ Full contributor guide: [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md)**
+**→ Full contributor guide: [docs/contributing.md](docs/contributing.md)**
 
 Quick essentials:
 
-- Development setup: [docs/DEVELOPMENT.md](docs/DEVELOPMENT.md)
-- Governance & legal: See [docs/CONTRIBUTING.md](docs/CONTRIBUTING.md)
+- Development setup: [docs/development.md](docs/development.md)
+- Governance & legal: See [docs/contributing.md](docs/contributing.md)
 - Code of Conduct: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
 
 ## Quick Start
 
-1. Fork and create a feature branch from `dev`
+1. Fork and create a feature branch from `main`
 1. Run local checks: `uv run poe check-all`
 1. Open a PR using `.github/PULL_REQUEST_TEMPLATE.md`
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dataenginex
-Version: 0.4.3
+Version: 0.4.4
 Summary: DataEngineX — open-source, self-hosted, local-first Data + ML + AI workbench library
 Author-email: Jay <jayapal.myaka99@gmail.com>
 License: MIT License
@@ -30,7 +30,6 @@ Requires-Dist: click>=8.3.3
 Requires-Dist: croniter>=6.2.2
 Requires-Dist: duckdb>=1.5.2
 Requires-Dist: httpx>=0.28.1
-Requires-Dist: msgpack>=1.2.1
 Requires-Dist: orjson>=3.11.0
 Requires-Dist: prometheus-client>=0.25.0
 Requires-Dist: pyarrow>=23.0.1
@@ -38,7 +37,6 @@ Requires-Dist: pydantic-settings>=2.14.2
 Requires-Dist: pydantic>=2.13.4
 Requires-Dist: pyyaml>=6.0.3
 Requires-Dist: structlog>=25.5.0
-Requires-Dist: zstandard>=0.25.0
 Provides-Extra: cloud
 Requires-Dist: boto3>=1.43.7; extra == 'cloud'
 Requires-Dist: google-cloud-bigquery>=3.41.0; extra == 'cloud'

{dataenginex-0.4.3 → dataenginex-0.4.4}/README.md

@@ -1,11 +1,11 @@
 # dataenginex
 
-[![CI](https://github.com/TheDataEngineX/dataenginex/actions/workflows/ci.yml/badge.svg?branch=dev)](https://github.com/TheDataEngineX/dataenginex/actions/workflows/ci.yml)
+[![CI](https://github.com/TheDataEngineX/dataenginex/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/TheDataEngineX/dataenginex/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/dataenginex)](https://pypi.org/project/dataenginex/)
 [![Python 3.13+](https://img.shields.io/badge/python-3.13+-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
 
-The Python library that powers [DEX Studio](https://github.com/TheDataEngineX/dex-studio) — an open-source, self-hosted, local-first Data + ML + AI workbench for individuals and small teams. **Use the library directly when you want code; install DEX Studio when you want a UI.**
+The Python library that powers [DataEngineX Studio](https://github.com/TheDataEngineX/dex-studio) — an open-source, self-hosted, local-first Data + ML + AI workbench for individuals and small teams. **Use the library directly when you want code; install DataEngineX Studio when you want a UI.**
 
 ______________________________________________________________________
 
@@ -116,7 +116,7 @@ git clone https://github.com/TheDataEngineX/dex-studio && cd dex-studio
 docker compose up             # http://localhost:7860
 ```
 
-DEX Studio imports `dataenginex` directly — no separate API server, no HTTP hop.
+DataEngineX Studio imports `dataenginex` directly — no separate API server, no HTTP hop.
 
 ______________________________________________________________________
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docker-compose.test.yml

@@ -1,5 +1,5 @@
 # ---------------------------------------------------------------
-# DEX — Storage Emulators for Integration Tests
+# DataEngineX — Storage Emulators for Integration Tests
 #
 # Spins up LocalStack (S3) and fake-gcs-server (GCS) for local
 # integration testing without real cloud accounts.

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/adr/0001-medallion-architecture.md

@@ -8,18 +8,18 @@
 
 ## Context
 
-DEX needs a scalable, standardized data architecture that works across all projects (CareerDEX, Weather, etc.). The data pipeline needs to handle:
+DataEngineX needs a scalable, standardized data architecture that works across all projects (CareerDEX, Weather, etc.). The data pipeline needs to handle:
 
 - Raw data ingestion from multiple sources
 - Data transformation and quality validation
 - Feature engineering for ML models
 - Analytics-ready data consumption
 
-Multiple projects will be built on the DEX platform, each with different data sources and transformations. We need a consistent, reusable pattern.
+Multiple projects will be built on the DataEngineX platform, each with different data sources and transformations. We need a consistent, reusable pattern.
 
 ## Decision
 
-Implement the **Medallion Architecture** (Bronze → Silver → Gold layers) as the standard data architecture for all DEX projects.
+Implement the **Medallion Architecture** (Bronze → Silver → Gold layers) as the standard data architecture for all DataEngineX projects.
 
 ### Architecture Layers
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/architecture.md

@@ -5,7 +5,7 @@
 **DataEngineX** is a unified Data + ML + AI **library** that wires industry tools through a
 single config-driven interface. One `dex.yaml` defines the entire project.
 
-**Design principle:** Pure Python library — no HTTP server bundled. Your application (DEX Studio,
+**Design principle:** Pure Python library — no HTTP server bundled. Your application (DataEngineX Studio,
 your own FastAPI/Flask app, a script) imports `dataenginex` and owns the server layer.
 
 ## Architecture
@@ -56,9 +56,9 @@ dex.yaml
 Every subsystem follows the same pattern:
 
 1. **ABC** in `core/interfaces.py` — defines the contract (e.g. `BaseConnector`)
-2. **BackendRegistry[T]** in `core/registry.py` — discovers and registers implementations
-3. **Built-in** implements the ABC with zero external deps
-4. **Extras** implement the same ABC, swapped in via config
+1. **BackendRegistry[T]** in `core/registry.py` — discovers and registers implementations
+1. **Built-in** implements the ABC with zero external deps
+1. **Extras** implement the same ABC, swapped in via config
 
 ```python
 from dataenginex.core.registry import BackendRegistry
@@ -108,10 +108,7 @@ DataEngineXError
 ├── ConfigError → ConfigValidationError
 ├── PipelineError → PipelineStepError
 ├── RegistryError
-├── BackendNotInstalledError
-├── TrainingError
-├── ServingError
-└── AgentError → LLMProviderError
+└── BackendNotInstalledError
 ```
 
 ## Module Map

dataenginex-0.4.4/docs/ci-cd.md

@@ -0,0 +1,97 @@
+# CI/CD Pipeline
+
+**Continuous integration and release automation for dataenginex.**
+
+______________________________________________________________________
+
+## Overview
+
+dataenginex is a pure Python library published to PyPI. The pipeline is:
+
+- **CI**: Linting, type checking, testing, and security scanning on every PR to `main`.
+- **Release**: Push a `v{X.Y.Z}` tag to `main` → `release.yml` builds, publishes to PyPI, and creates a GitHub Release.
+
+```mermaid
+graph LR
+    Dev[Developer] --> PR[Open PR to main]
+    PR --> CI[CI: Lint/Test/Security]
+    CI --> Review[Code Review]
+    Review --> Merge["Merge to main"]
+    Merge --> Tag["Push tag vX.Y.Z"]
+    Tag --> Release[release.yml]
+    Release --> Build["Build wheel + sdist"]
+    Build --> PyPI["Publish to PyPI (OIDC)"]
+    Build --> GHRelease["GitHub Release + CycloneDX SBOM"]
+```
+
+______________________________________________________________________
+
+## Continuous Integration (CI)
+
+**Workflow**: `.github/workflows/ci.yml`
+
+**Triggers**:
+
+- Push to `main`
+- Pull requests targeting `main`
+
+**Jobs**:
+
+### 1. Quality (`quality`)
+
+```bash
+uv run ruff check src/ tests/
+uv run mypy src/dataenginex/ --strict
+```
+
+### 2. Test (`test`)
+
+```bash
+uv run pytest tests/ -x --tb=short --cov=src/dataenginex/
+```
+
+Coverage threshold: 80%.
+
+### 3. Package validation
+
+```bash
+uv build
+```
+
+### 4. Security Scans
+
+Runs via the shared reusable workflow at `.github/workflows/security.yml`:
+
+- **Trivy**: Misconfig and secret scan — results uploaded to GitHub Security tab.
+- **CodeQL**: Handled by GitHub's default setup.
+
+______________________________________________________________________
+
+## Release Automation
+
+**Workflow**: `.github/workflows/release.yml`
+
+**Trigger**: Push a tag matching `v[0-9]+.[0-9]+.[0-9]+` to `main`.
+
+**Jobs**:
+
+1. **build** — `uv build` → upload wheel + sdist
+1. **publish-pypi** — `pypa/gh-action-pypi-publish` (OIDC trusted publishing)
+1. **github-release** — CycloneDX SBOM → `gh release create`
+
+**How to release**:
+
+```bash
+git tag v1.2.3
+git push origin v1.2.3
+```
+
+______________________________________________________________________
+
+## Workflows Overview
+
+| Workflow | Trigger | Purpose |
+| --- | --- | --- |
+| **CI** | Push/PR to main | Lint + typecheck + test + security |
+| **Security** | Push/PR to main | Trivy misconfig + secret scan |
+| **Release** | Push tag `v*.*.*` to main | Build → PyPI → GitHub Release |

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/contributing.md

@@ -1,4 +1,4 @@
-# Contributing to DEX
+# Contributing to DataEngineX
 
 Thank you for contributing!
 
@@ -6,7 +6,7 @@ Thank you for contributing!
 
 1. Read [development.md](./development.md) for setup instructions
 1. Fork the repository
-1. Create a feature branch from `dev`
+1. Create a feature branch from `main`
 1. Make your changes
 1. Submit a pull request
 
@@ -68,7 +68,7 @@ Use semantic commit format:
 
 - This project is open source under MIT; keep license and attribution notices in redistributions.
 - Forks are welcome, but should use a distinct public name when redistributed as a separate project.
-- Do not present a fork as the official DataEngineX/DEX project.
+- Do not present a fork as the official DataEngineX project.
 - See the project's license and brand guidelines for brand-usage details.
 
 ## Code Reviews
@@ -94,7 +94,7 @@ uv run poe check-all   # Run all checks
 - `enhancement` - New feature or improvement
 - `good first issue` - Good for newcomers
 - `P1-high` / `P2-medium` - Priority levels
-- `dex-module` - Core DEX infrastructure
+- `dex-module` - Core DataEngineX infrastructure
 
 ## Questions?
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/development.md

@@ -39,7 +39,7 @@ This installs all Python dependencies and configures pre-commit hooks.
 # 1. Clone repo and create feature branch
 git clone https://github.com/TheDataEngineX/dataenginex.git
 cd dataenginex
-git checkout -b feat/issue-XXX-description dev
+git checkout -b my-feature-branch main
 
 # 2. Install Python deps & pre-commit hooks
 uv run poe setup
@@ -68,8 +68,8 @@ dataenginex/
 ### Branch & Commit
 
 ```bash
-# 1. Create feature branch from dev
-git checkout -b feat/issue-XXX-description dev
+# 1. Create a feature branch from main
+git checkout -b my-feature-branch main
 
 # 2. Make changes to src/
 # Add tests in tests/
@@ -83,7 +83,7 @@ uv run poe test
 git commit -m "feat(#XXX): description"
 
 # 5. Push & create PR
-git push origin feat/issue-XXX-description
+git push origin my-feature-branch
 ```
 
 **PR Requirements:**
@@ -91,11 +91,11 @@ git push origin feat/issue-XXX-description
 - Link to issue: `Closes #XXX`
 - All checks pass (CI/CD ~3-5 min)
 - 1 approval required
-- Merge to `dev` when ready
+- Merge to `main` when ready
 
 ### Version Management
 
-DEX has a single version source:
+DataEngineX has a single version source:
 
 - **dataenginex version**: root `pyproject.toml` — managed automatically by the `release.yml` workflow
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/quickstart.md

@@ -140,9 +140,9 @@ events = engine.secops_audit.events   # list of AuditEvent
 
 ______________________________________________________________________
 
-## DEX Studio
+## DataEngineX Studio
 
-DEX Studio is the optional web UI that loads a `dex.yaml` and provides a single
+DataEngineX Studio is the optional web UI that loads a `dex.yaml` and provides a single
 control plane for Data / ML / AI / System. It uses `dataenginex` directly as a library
 — no separate server process needed.
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/sdlc.md

@@ -6,7 +6,7 @@
 
 ______________________________________________________________________
 
-This document defines the software development lifecycle (SDLC) for DEX, including the required stages, artifacts, and quality gates.
+This document defines the software development lifecycle (SDLC) for DataEngineX, including the required stages, artifacts, and quality gates.
 
 ## Goals
 
@@ -14,28 +14,6 @@ This document defines the software development lifecycle (SDLC) for DEX, includi
 - Enforce quality gates (lint, test, type checks, security scan) on every PR.
 - Maintain a complete audit trail for promotion across environments.
 
-## Lifecycle Overview
-
-```mermaid
-graph LR
-    Plan[1. Plan] --> Design[2. Design]
-    Design --> Implement[3. Implement]
-    Implement --> Verify[4. Verify CI]
-    Verify --> Release[5. Release CD]
-    Release --> Operate[6. Operate]
-    Operate -->|Issues| Plan
-    Operate -->|Incidents| Rollback[Rollback]
-    Rollback --> Operate
-
-    style Plan fill:#e1f5ff
-    style Design fill:#e1f5ff
-    style Implement fill:#fff3cd
-    style Verify fill:#fff3cd
-    style Release fill:#d4edda
-    style Operate fill:#d4edda
-    style Rollback fill:#f8d7da
-```
-
 ## Lifecycle Stages
 
 ### 1) Plan
@@ -89,7 +67,7 @@ ______________________________________________________________________
 
 ### 4) Verify (CI)
 
-**Entry**: Pull request opened against `dev` (integration) or `main` (release).
+**Entry**: Pull request opened against `main`.
 
 **Required Checks**:
 
@@ -107,8 +85,7 @@ ______________________________________________________________________
 
 **Entry**:
 
-- Dev deployment: PR merged to `dev`.
-- Stage/Prod deployment: PR merged to `main`.
+- PR merged to `main`.
 
 **Actions**:
 
@@ -141,49 +118,29 @@ ______________________________________________________________________
 ```mermaid
 flowchart TD
     Start([New Feature/Fix]) --> Issue[Create GitHub Issue]
-    Issue --> Branch["Create branch: feat/xyz"]
+    Issue --> Branch["Create branch: my-feature"]
     Branch --> Code[Implement + Tests]
     Code --> Local["Local checks: lint, test, types"]
     Local -->|Failed| Code
-    Local -->|Passed| PR["Open PR → dev"]
+    Local -->|Passed| PR["Open PR → main"]
     PR --> CI{CI Checks}
     CI -->|Failed| Fix[Fix Issues]
     Fix --> Code
     CI -->|Passed| Review{Code Review}
     Review -->|Changes Requested| Code
-    Review -->|Approved| MergeDev["Merge to dev"]
-    MergeDev --> DevDeploy[Auto-deploy to dev]
-    DevDeploy --> DevTest{Dev Tests Pass?}
-    DevTest -->|Failed| Hotfix[Hotfix or Rollback]
-    Hotfix --> Code
-    DevTest -->|Passed| ReleasePR["Create PR: dev → main"]
-    ReleasePR --> ReleaseCI{CI Checks}
-    ReleaseCI -->|Failed| Fix
-    ReleaseCI -->|Passed| ReleaseReview{Code Review}
-    ReleaseReview -->|Changes Requested| Code
-    ReleaseReview -->|Approved| MergeMain["Merge to main"]
-    MergeMain --> ProdDeploy[Auto-deploy to stage+prod]
-    ProdDeploy --> Monitor[Monitor Production]
+    Review -->|Approved| MergeMain["Merge to main"]
+    MergeMain --> Prod[Auto-release if tagged]
+    Prod --> Monitor[Monitor]
     Monitor --> End([✓ Complete])
-
-    style Start fill:#e1f5ff
-    style Issue fill:#e1f5ff
-    style Code fill:#fff3cd
-    style CI fill:#fff3cd
-    style Review fill:#fff3cd
-    style DevDeploy fill:#d4edda
-    style ProdDeploy fill:#d4edda
-    style End fill:#d4edda
-    style Hotfix fill:#f8d7da
 ```
 
 **Steps**:
 
-1. Create or update a GitHub Issue and add it to the GitHub Project board.
-1. Create a feature branch and implement changes.
-1. Open a PR to `dev` and request review.
-1. After validation in dev, open a release PR from `dev` → `main`.
+1. Create a feature branch from `main`.
+1. Implement changes, run local checks (`uv run poe check-all`).
+1. Open a PR to `main` and request review.
 1. Merge after all required checks pass.
+1. Push a `vX.Y.Z` tag to trigger a PyPI release.
 
 See [Contributing Guide](contributing.md) for branch naming, local checks, and PR conventions.
 

{dataenginex-0.4.3 → dataenginex-0.4.4}/docs/security-scanning.md

@@ -11,7 +11,7 @@ DataEngineX uses a multi-layered security scanning pipeline across CI/CD workflo
 | **CodeQL** | Static analysis (Python + GitHub Actions) | `security.yml` |
 | **pip-audit** | Python dependency vulnerability audit | `poe security` |
 | **CycloneDX** | SBOM generation (attached to releases) | `release-*.yml` |
-| **Dependabot** | Automated dependency updates | `.github/dependabot.yml` |
+| **Renovate** | Automated dependency updates | `renovate.json` |
 
 ## How It Works
 
@@ -30,7 +30,7 @@ DataEngineX uses a multi-layered security scanning pipeline across CI/CD workflo
    trivy image dex:local
    ```
 
-### On Release (release-dataenginex.yml)
+### On Release (release.yml)
 
 1. **CycloneDX SBOM** — generates a Software Bill of Materials in CycloneDX JSON format.
 1. **SBOM upload** — attaches the SBOM as a release asset on GitHub Releases.

{dataenginex-0.4.3 → dataenginex-0.4.4}/examples/01_hello_pipeline.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python
-"""01_hello_pipeline.py — Minimal DEX pipeline walkthrough.
+"""01_hello_pipeline.py — Minimal DataEngineX pipeline walkthrough.
 
 Demonstrates:
 - Data profiling with ``DataProfiler``

{dataenginex-0.4.3 → dataenginex-0.4.4}/examples/02_api_quickstart.py

@@ -44,7 +44,7 @@ def create_app() -> FastAPI:
     app = FastAPI(
         title="DataEngineX",
         version="0.8.9",
-        description="Example DEX API instance",
+        description="Example DataEngineX API instance",
     )
 
     @app.get("/")

{dataenginex-0.4.3 → dataenginex-0.4.4}/examples/07_api_ingestion.py

@@ -5,7 +5,7 @@ Demonstrates:
 - Fetching data from an external HTTP API (OpenWeatherMap-style)
 - Transforming raw responses into standardized records (Bronze → Silver)
 - Validating data quality before promotion (Silver → Gold)
-- Using DEX QualityGate for data validation
+- Using DataEngineX QualityGate for data validation
 
 Run:
     uv run python examples/07_api_ingestion.py