This release is a pre-release and may not be stable for production use.
IntentumDiff
Semantic code review — see what a change means, not which lines moved.
A textual diff shows that 40 lines changed. It cannot tell you whether that is a rename, a function moved between files, a reformat, or a behavioural change hiding among them. IntentumDiff parses both sides, matches the trees, and classifies every change by what it does: meaningful, refactoring, moved, or ignored style.
Install
pip install --pre intentumdiff-python
0.0.3b1 is a pre-release, so --pre is needed. Without it pip finds no installable version,
because the only stable release, 0.0.1, has been yanked.
Requires Python 3.12+. The wheel bundles the Rust engine and language parser
components; built-in parsing needs no separate component download.
Platform limitation: PowerShell is unavailable on Windows ARM64 because of the tracked compiler limitation in #42. Rust reports this parser as unavailable; the package does not substitute a Python engine.
The distribution is
intentumdiff-python; the import package isintentumdiff.
Quick start
from intentumdiff import SemanticDiffer
old = """def greet(name):
return 'hi ' + name
"""
new = """def greet(name):
if not name:
return None
return 'hi ' + name
"""
diff = SemanticDiffer().diff_strings(old, new, "example.py")
for change in diff.changes:
print(change.change_type, change.description)
ChangeType.ADDITION Insert -> if_statement('if_statement')
A line diff reports three added lines. IntentumDiff reports that a guard clause was introduced — the thing a reviewer needs to know.
Command line
intentumdiff --help # or: python -m intentumdiff --help
intentumdiff file old.py new.py
intentumdiff git --help # diff against a ref in a git repository
See the CLI
This real installed-wheel recording changes the assigned value from 1 to 2.
Rust reports one modification; the main diff panel and table use rs-rich.
Watch the CLI examples and read their exact provenance. The recordings use the verified Python #98 Linux wheel (an earlier 0.0.2b1 candidate) and rs-rich-record; they predate 0.0.3b1. Standalone guardrail reports and errors still use the existing presentation paths.
Complete, equivalent and incomplete reviews
Every diff says how complete it is, in diff.completeness. The verdict comes from the
engine; Python never guesses it.
completeness |
Meaning |
|---|---|
"complete" |
diff.changes is the review. |
"equivalent" |
The sources differ, but the engine proved they mean the same thing (for example JSON keys that were only reordered). diff.metadata["equivalence_proof"] names the rule when there is one. |
"incomplete" |
The sources differ, but the engine could not explain the change. This is not "no changes". |
For an incomplete review, diff.incomplete.message is the engine's explanation and
diff.incomplete.source_ranges lists the line ranges it could not explain. The CLI prints
that message in place of "No changes detected", and repeats it on stderr.
Reporting a bug: --report-bug
When a review is incomplete, the CLI can help you report it. With --report-bug (on
file, git, patch and string), or when run in an interactive terminal, it prints the
issue title and body the engine wrote and asks [y/N] before opening anything:
intentumdiff file old.py new.py --report-bug
Only an explicit y opens the pre-filled GitHub issue in your browser. If the link can
only carry a shortened report, the CLI says so; the printed body is the full report to
paste. Without a terminal nothing is ever opened. The report holds only the engine's text:
no file names, paths or source code. All of this goes to stderr, so JSON and other machine
output are unchanged.
Documentation
https://buchochelliq-labs.github.io/intentumdiff-docs/
There is also a VS Code extension, which uses this package as its engine.
Privacy
Everything runs locally and there is no telemetry. The optional LLM explainer is off by default and bring-your-own-key; when enabled for a cloud endpoint it sends a privacy-safe fact sheet — counts, categories and flags — never your source, identifiers or literals. See the privacy policy.
Licence
MIT. Contributing and build-from-source instructions are in CONTRIBUTING.md.
Metadata
Release files for intentumdiff-python 0.0.3b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| intentumdiff_python-0.0.3b1-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details for intentumdiff_python-0.0.3b1-py3-none-win_arm64.whl |
| intentumdiff_python-0.0.3b1-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for intentumdiff_python-0.0.3b1-py3-none-win_amd64.whl |
| intentumdiff_python-0.0.3b1-py3-none-manylinux_2_39_x86_64.whl | Python 3 | none | Linux glibc 2.39+ x86-64 | Details for intentumdiff_python-0.0.3b1-py3-none-manylinux_2_39_x86_64.whl |
| intentumdiff_python-0.0.3b1-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for intentumdiff_python-0.0.3b1-py3-none-macosx_11_0_arm64.whl |
Total release size: 92.6 MB
Release files / intentumdiff_python-0.0.3b1-py3-none-win_arm64.whl
| Download URL | intentumdiff_python-0.0.3b1-py3-none-win_arm64.whl |
|---|---|
| Size | 22.5 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
a25f970dcf9127fec6292147673d868e2b8f537a5a5136a082981d304aa631a9
|
|
BLAKE2b-256 checksum How to use checksums |
8d9d3e6b136afac52a3b748ce18fc00ff33aa74c49421bf074ae3bd3b79eb0b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / intentumdiff_python-0.0.3b1-py3-none-win_amd64.whl
| Download URL | intentumdiff_python-0.0.3b1-py3-none-win_amd64.whl |
|---|---|
| Size | 23.9 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
01f884b5eee8cb31be6efd98d75b4124ac56f13aa14ed1936590b907689e84e0
|
|
BLAKE2b-256 checksum How to use checksums |
93ed19f18bc1e832d469709bfb52e90dd9cc6c5d813707dd0298fdf920635470
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / intentumdiff_python-0.0.3b1-py3-none-manylinux_2_39_x86_64.whl
| Download URL | intentumdiff_python-0.0.3b1-py3-none-manylinux_2_39_x86_64.whl |
|---|---|
| Size | 24.1 MB |
| Tags | Linux glibc 2.39+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
42f473ae34dce6d78dfe19c86c3bf1c8967ba658b6059c8185b669df78ae34ec
|
|
BLAKE2b-256 checksum How to use checksums |
92d17978e6627015936e593c7a73ff60df3a53411c929f8f13ad130ba4775f08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / intentumdiff_python-0.0.3b1-py3-none-macosx_11_0_arm64.whl
| Download URL | intentumdiff_python-0.0.3b1-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 22.1 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0dcf13408817b4bda4bee7b2b9083a160161ea9af0276d2b060ec327e94e78aa
|
|
BLAKE2b-256 checksum How to use checksums |
84f73fdd850b5f515b20301d07764459d6293aecb2f8d2ba106eeb97d2572ac2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for intentumdiff-python 0.0.3b1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.