OpenBlame
_ _
| | | |
___ _ __ ___ _ __ | |__ | | __ _ _ __ ___ ___
/ _ \| '_ \ / _ \ '_ \| '_ \| |/ _` | '_ ` _ \ / _ \
| (_) | |_) | __/ | | | |_) | | (_| | | | | | | __/
\___/| .__/ \___|_| |_|_.__/|_|\__,_|_| |_| |_|\___|
| |
|_|
OpenBlame is a local-first AI investigation CLI for data pipelines running on OpenMetadata. Point it to a table, and it will trace lineage, inspect recent quality failures, parse schema-changes, surface governance gaps, and draft a root-cause narrative.
The reasoning layer runs entirely on your local Ollama models, ensuring your metadata stays inside your environment.
Features
- Autonomous Investigation: ReAct-style agent loop that plans and executes metadata research.
- Lineage & Blast Radius: Automatic upstream/downstream analysis to find affected entities.
- Schema Drift: Instant diffing of column changes, type updates, and renames.
- Governance Aware: Surfaces missing owners, tiers, and domain gaps as operational risks.
- Local-First AI: Powered by Ollama (qwen2.5, llama3, etc.). No external API keys needed for reasoning.
- MCP Ready: Built-in Model Context Protocol server to integrate with AI IDEs like Cursor and Claude Desktop.
Quick Start
1. Install
pip install openblame
2. Configure (CLI-only)
No need to manually edit files. Just run the interactive setup:
openblame configure
It will help you set your OpenMetadata Host, Token, and even auto-detect your installed Ollama models.
3. Investigate
openblame investigate "ecommerce.analytics.customer_churn"
CLI Commands
investigate
The core command. Runs the full AI reasoning loop.
openblame investigate <table_fqn> [OPTIONS]
Options:
--depth INTEGER Lineage depth (default: 3)
--days INTEGER Lookback days for changes (default: 7)
--output PATH Save report to markdown file
--model TEXT Override default Ollama model
--host TEXT Override OpenMetadata host
--token TEXT Override OpenMetadata JWT token
configure
Interactive setup for your environment. Sets up .env for you.
openblame configure
list-models
Show all models available in your local Ollama instance and see which one is active.
openblame list-models
diff
Check for schema changes in a table without running the full agent.
openblame diff <table_fqn> --days 7
lineage
Visualize upstream and downstream lineage as a tree.
openblame lineage <table_fqn> --depth 3
mcp-server
Start the MCP server for integration with Claude/Cursor.
openblame mcp-server
MCP Integration (Cursor / Claude)
Add OpenBlame to your claude_desktop_config.json:
{
"mcpServers": {
"openblame": {
"command": "openblame",
"args": ["mcp-server"]
}
}
}
Development
# Clone and install
git clone https://github.com/manasdutta04/openblame
cd openblame
pip install -e ".[dev]"
# Run Tests (Windows)
.\test.ps1
# Run Tests (Linux/Mac)
make test
License
OpenBlame is released under the MIT License. See LICENSE for details.
Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines. Check out our Code of Conduct and Security Policy.
Metadata
Release files for openblame 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openblame-0.1.8.tar.gz | 23.4 kB | With provenance | Details for openblame-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openblame-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for openblame-0.1.8-py3-none-any.whl |
Total release size: 45.7 kB
Release files / openblame-0.1.8.tar.gz
| Download URL | openblame-0.1.8.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f22438ce4856b44c36b6c47e4beec7b2939dc42ae9b6f8eac66c71f9daee6d0
|
|
BLAKE2b-256 checksum How to use checksums |
70ba1e045a42c4b852e076f10445cd8df57e9e877a9653cb11090cde4305d301
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logRelease files / openblame-0.1.8-py3-none-any.whl
| Download URL | openblame-0.1.8-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c719fb1e745ba705fc6b8da4b3a436461c2270119ae883c5d10c440218ffd79f
|
|
BLAKE2b-256 checksum How to use checksums |
c86f13de72c0c69f310f08135acdeb511b37061156a7cefa8770a421c4afcab3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logSecurity for openblame 0.1.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for openblame-0.1.8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.