dataranger 0.0.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- dataranger-0.0.1/.github/workflows/release.yml +34 -0
- dataranger-0.0.1/.gitignore +6 -0
- dataranger-0.0.1/LICENSE +21 -0
- dataranger-0.0.1/PKG-INFO +49 -0
- dataranger-0.0.1/README.md +31 -0
- dataranger-0.0.1/pyproject.toml +33 -0
- dataranger-0.0.1/src/dataranger/__init__.py +3 -0
- dataranger-0.0.1/src/dataranger/cli.py +31 -0
- dataranger-0.0.1/tests/test_cli.py +12 -0
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
name: release
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
tags: ["v*"]
|
|
6
|
+
|
|
7
|
+
jobs:
|
|
8
|
+
build:
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
steps:
|
|
11
|
+
- uses: actions/checkout@v4
|
|
12
|
+
- uses: actions/setup-python@v5
|
|
13
|
+
with:
|
|
14
|
+
python-version: "3.12"
|
|
15
|
+
- run: python -m pip install build pytest
|
|
16
|
+
- run: pip install -e . && pytest -q
|
|
17
|
+
- run: python -m build
|
|
18
|
+
- uses: actions/upload-artifact@v4
|
|
19
|
+
with:
|
|
20
|
+
name: dist
|
|
21
|
+
path: dist/
|
|
22
|
+
|
|
23
|
+
publish:
|
|
24
|
+
needs: build
|
|
25
|
+
runs-on: ubuntu-latest
|
|
26
|
+
environment: pypi
|
|
27
|
+
permissions:
|
|
28
|
+
id-token: write
|
|
29
|
+
steps:
|
|
30
|
+
- uses: actions/download-artifact@v4
|
|
31
|
+
with:
|
|
32
|
+
name: dist
|
|
33
|
+
path: dist/
|
|
34
|
+
- uses: pypa/gh-action-pypi-publish@release/v1
|
dataranger-0.0.1/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Akshay Sharma
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: dataranger
|
|
3
|
+
Version: 0.0.1
|
|
4
|
+
Summary: An agent that patrols your data, fixes what it can prove, and calls you for the rest.
|
|
5
|
+
Project-URL: Homepage, https://github.com/akshaysharma1088/dataranger
|
|
6
|
+
Project-URL: Issues, https://github.com/akshaysharma1088/dataranger/issues
|
|
7
|
+
Author-email: Akshay Sharma <akshay.sharma1088@gmail.com>
|
|
8
|
+
License-Expression: MIT
|
|
9
|
+
License-File: LICENSE
|
|
10
|
+
Keywords: agents,data engineering,data observability,data quality,llm,verification
|
|
11
|
+
Classifier: Development Status :: 1 - Planning
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: Programming Language :: Python :: 3
|
|
14
|
+
Classifier: Topic :: Database
|
|
15
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
16
|
+
Requires-Python: >=3.10
|
|
17
|
+
Description-Content-Type: text/markdown
|
|
18
|
+
|
|
19
|
+
# DataRanger
|
|
20
|
+
|
|
21
|
+
**DataRanger patrols your data, fixes what it can prove, and calls you for the rest.**
|
|
22
|
+
|
|
23
|
+
A park ranger patrols the trails, fixes what is safe to fix on the spot, calls in anything dangerous, and files a report. DataRanger does the same for your tables.
|
|
24
|
+
|
|
25
|
+
Most data-quality tools stop at an alert. Letting an AI agent fix data is the obvious next step, and a risky one: a wrong fix can pass every monitor you have. DataRanger only applies a fix after it has been **proven against source data**, and it hands everything else to a person with the evidence attached.
|
|
26
|
+
|
|
27
|
+
## The patrol loop
|
|
28
|
+
|
|
29
|
+
1. **Detect.** Rules and statistics find nulls, duplicates, schema drift, late partitions, broken references, unit errors and silent shifts. No LLM.
|
|
30
|
+
2. **Diagnose.** A language model answers one narrow question: what is the likely cause?
|
|
31
|
+
3. **Propose fix.** A templated fix (dedupe, backfill, quarantine, patch). The model fills in parameters only.
|
|
32
|
+
4. **Verify.** [pipeverify](https://github.com/akshaysharma1088/pipeverify) checks the fix against source data, on a copy.
|
|
33
|
+
5. **Gate.** Proven and low risk: applied as a new version, never an overwrite. Anything else: escalated.
|
|
34
|
+
6. **Report.** Every detection, fix and decision lands on a live dashboard and an audit log.
|
|
35
|
+
|
|
36
|
+
## Status
|
|
37
|
+
|
|
38
|
+
Early. Version 0.0.1 reserves the name and ships the command-line skeleton:
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
pip install dataranger
|
|
42
|
+
dataranger plan
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
The first working patrol loop (DuckDB, open-weights models through Ollama, static dashboard) is planned for 0.1.0, alongside the DQ-Repair benchmark.
|
|
46
|
+
|
|
47
|
+
## License
|
|
48
|
+
|
|
49
|
+
MIT
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# DataRanger
|
|
2
|
+
|
|
3
|
+
**DataRanger patrols your data, fixes what it can prove, and calls you for the rest.**
|
|
4
|
+
|
|
5
|
+
A park ranger patrols the trails, fixes what is safe to fix on the spot, calls in anything dangerous, and files a report. DataRanger does the same for your tables.
|
|
6
|
+
|
|
7
|
+
Most data-quality tools stop at an alert. Letting an AI agent fix data is the obvious next step, and a risky one: a wrong fix can pass every monitor you have. DataRanger only applies a fix after it has been **proven against source data**, and it hands everything else to a person with the evidence attached.
|
|
8
|
+
|
|
9
|
+
## The patrol loop
|
|
10
|
+
|
|
11
|
+
1. **Detect.** Rules and statistics find nulls, duplicates, schema drift, late partitions, broken references, unit errors and silent shifts. No LLM.
|
|
12
|
+
2. **Diagnose.** A language model answers one narrow question: what is the likely cause?
|
|
13
|
+
3. **Propose fix.** A templated fix (dedupe, backfill, quarantine, patch). The model fills in parameters only.
|
|
14
|
+
4. **Verify.** [pipeverify](https://github.com/akshaysharma1088/pipeverify) checks the fix against source data, on a copy.
|
|
15
|
+
5. **Gate.** Proven and low risk: applied as a new version, never an overwrite. Anything else: escalated.
|
|
16
|
+
6. **Report.** Every detection, fix and decision lands on a live dashboard and an audit log.
|
|
17
|
+
|
|
18
|
+
## Status
|
|
19
|
+
|
|
20
|
+
Early. Version 0.0.1 reserves the name and ships the command-line skeleton:
|
|
21
|
+
|
|
22
|
+
```bash
|
|
23
|
+
pip install dataranger
|
|
24
|
+
dataranger plan
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
The first working patrol loop (DuckDB, open-weights models through Ollama, static dashboard) is planned for 0.1.0, alongside the DQ-Repair benchmark.
|
|
28
|
+
|
|
29
|
+
## License
|
|
30
|
+
|
|
31
|
+
MIT
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["hatchling"]
|
|
3
|
+
build-backend = "hatchling.build"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "dataranger"
|
|
7
|
+
dynamic = ["version"]
|
|
8
|
+
description = "An agent that patrols your data, fixes what it can prove, and calls you for the rest."
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
license = "MIT"
|
|
11
|
+
requires-python = ">=3.10"
|
|
12
|
+
authors = [{ name = "Akshay Sharma", email = "akshay.sharma1088@gmail.com" }]
|
|
13
|
+
keywords = ["data quality", "data engineering", "agents", "llm", "verification", "data observability"]
|
|
14
|
+
classifiers = [
|
|
15
|
+
"Development Status :: 1 - Planning",
|
|
16
|
+
"Intended Audience :: Developers",
|
|
17
|
+
"Programming Language :: Python :: 3",
|
|
18
|
+
"Topic :: Database",
|
|
19
|
+
"Topic :: Software Development :: Quality Assurance",
|
|
20
|
+
]
|
|
21
|
+
|
|
22
|
+
[project.urls]
|
|
23
|
+
Homepage = "https://github.com/akshaysharma1088/dataranger"
|
|
24
|
+
Issues = "https://github.com/akshaysharma1088/dataranger/issues"
|
|
25
|
+
|
|
26
|
+
[project.scripts]
|
|
27
|
+
dataranger = "dataranger.cli:main"
|
|
28
|
+
|
|
29
|
+
[tool.hatch.version]
|
|
30
|
+
path = "src/dataranger/__init__.py"
|
|
31
|
+
|
|
32
|
+
[tool.hatch.build.targets.wheel]
|
|
33
|
+
packages = ["src/dataranger"]
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
"""Command-line entry point. The patrol loop lands in 0.1.0; this release reserves the name."""
|
|
2
|
+
import argparse
|
|
3
|
+
|
|
4
|
+
from . import __version__
|
|
5
|
+
|
|
6
|
+
STAGES = [
|
|
7
|
+
("Detect", "rules and statistics find the problem; no LLM"),
|
|
8
|
+
("Diagnose", "an LLM answers one narrow question about the cause"),
|
|
9
|
+
("Propose fix", "a templated fix; the LLM fills parameters only"),
|
|
10
|
+
("Verify", "pipeverify checks the fix against source data, on a copy"),
|
|
11
|
+
("Gate", "apply as a new version if proven and low risk; otherwise escalate"),
|
|
12
|
+
("Report", "every decision lands on the dashboard and the audit log"),
|
|
13
|
+
]
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
def main(argv=None):
|
|
17
|
+
parser = argparse.ArgumentParser(prog="dataranger", description=__doc__)
|
|
18
|
+
parser.add_argument("--version", action="version", version=f"dataranger {__version__}")
|
|
19
|
+
sub = parser.add_subparsers(dest="command")
|
|
20
|
+
sub.add_parser("plan", help="show the patrol loop DataRanger will run")
|
|
21
|
+
args = parser.parse_args(argv)
|
|
22
|
+
if args.command == "plan":
|
|
23
|
+
for i, (name, what) in enumerate(STAGES, 1):
|
|
24
|
+
print(f"{i}. {name}: {what}")
|
|
25
|
+
return 0
|
|
26
|
+
parser.print_help()
|
|
27
|
+
return 0
|
|
28
|
+
|
|
29
|
+
|
|
30
|
+
if __name__ == "__main__":
|
|
31
|
+
raise SystemExit(main())
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
from dataranger import __version__
|
|
2
|
+
from dataranger.cli import main
|
|
3
|
+
|
|
4
|
+
|
|
5
|
+
def test_version_string():
|
|
6
|
+
assert __version__.count(".") == 2
|
|
7
|
+
|
|
8
|
+
|
|
9
|
+
def test_plan_lists_six_stages(capsys):
|
|
10
|
+
assert main(["plan"]) == 0
|
|
11
|
+
out = capsys.readouterr().out.strip().splitlines()
|
|
12
|
+
assert len(out) == 6 and out[3].startswith("4. Verify")
|