converge-cli 0.1.7

Scan a Python repository, build a repo-local dependency graph, diagnose drift, create an environment, and apply validated manifest repairs.

Why Converge

Dependency tools usually answer one narrow question: what is in the manifest, what is in the lockfile, or what can be installed. Converge looks at the repository as a system.

It reads manifests, parses imports, stores a graph inside the target repo, and uses that graph to explain what is missing, unused, or ready to repair. Every command is scoped to the path you pass in, so running Converge from one directory never silently writes state into another project.

repo path -> scan -> .converge/graph.db -> doctor/explain/create/fix/export

What It Does Today

Converge is intentionally conservative: repairs are validated in isolation before host manifests are changed, and current repair planning focuses on dependency additions for unresolved imports.

Install

uv tool install converge-cli

or:

pipx install converge-cli

For local development:

git clone <your-repo-url>
cd converge
uv sync --dev

Quick Start

Given a repository with:

import requests

and a manifest that does not declare requests:

[project]
name = "demo"
dependencies = []

Run:

converge scan .
converge doctor .
converge fix .
converge fix . --apply

After validation, Converge updates the target repository manifest and records the repair in .converge/audit.log.

Command Guide

Scan

converge scan /path/to/repo
converge scan /path/to/repo --dry-run

scan builds the graph from declared dependencies, imports, and detected services. Without --dry-run, the graph is persisted to /path/to/repo/.converge/graph.db.

Doctor

converge doctor /path/to/repo

doctor exits 0 when no actionable issues are found and 1 when dependency issues are detected. If no graph exists, it exits with an error and tells you to run scan.

Explain

converge explain conflict:unresolved_mod:main.py_pkg:requests /path/to/repo
converge explain pkg:requests /path/to/repo

Use explain when you want the graph context behind a conflict or entity.

Create

converge create /path/to/repo --provider uv
converge create /path/to/repo --provider uv --python 3.12

create loads the repository graph, creates /path/to/repo/.venv, installs graph package nodes, and prints the activation command.

Fix

converge fix /path/to/repo
converge fix /path/to/repo --apply

Dry-run mode prints candidate plans and changes nothing. --apply validates a plan in an isolated sandbox, writes the selected manifest repair, and appends an audit event.

Export

converge export /path/to/repo --format json
converge export /path/to/repo --format csv

JSON export writes .converge/exports/graph.json. CSV export writes .converge/exports/nodes.csv and .converge/exports/edges.csv.

Clean

converge clean /path/to/repo

Removes generated artifacts such as .converge/graph.db, .converge/exports/, .converge/scan_state.json, .converge/audit.log, and .venv-converge-test.

Repository-Local State

Converge writes derived state inside the target repository:

JSON and Exit Codes

Global flags:

converge --json doctor /path/to/repo
converge --quiet scan /path/to/repo
converge --verbose doctor /path/to/repo

--json payloads include:

{
  "schema_version": 1,
  "tool_version": "0.1.7"
}

Exit codes:

Configuration

Settings are read from optional .converge.toml and [tool.converge] in pyproject.toml. When both exist, pyproject.toml wins on conflicts.

Useful keys include:

[tool.converge]
incremental_scan = true
skip_type_checking_imports = true
repair_targets = ["pyproject", "requirements"]
extra_scan_roots = ["src"]

See docs/ROADMAP.md for the current implementation map and remaining stretch work.

Development

Run the full verified suite:

TMPDIR=/tmp PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src .venv/bin/pytest tests/unit tests/integration -v

Lint and type check:

.venv/bin/ruff check .
.venv/bin/mypy src/converge

Coverage:

PYTHONPATH=src .venv/bin/pytest tests --cov=converge --cov-report=term-missing

Key implementation files:

Current Limits

Converge is useful now, but it does not overstate what the implementation proves.

• Repair planning is focused on dependency additions, not broad manifest rewrites.
• Validation is smoke-import based, not a full application test harness.
• Import classification is Python-focused and conservative.
• Export formats are designed for inspection and automation, not analytics warehousing.

License

MIT. See LICENSE.