gaze-py 0.2.0

Python-native GazeCRAP analysis engine

gaze-py

gaze-py is a Python-native port of gaze, the GazeCRAP analysis engine. It detects observable side effects in Python functions using AST-only static analysis (no code execution, no imports of analysed modules), classifies each effect as contractual or incidental using a five-signal confidence engine, and computes CRAP and GazeCRAP scores to surface functions that are both complex and under-tested. The output is schema-compatible with the Go gaze implementation.

Requirements

• Python 3.11+

Installation

# Run without installing (recommended for one-off use)
uvx --from gaze-py gazepy --help

# Permanent install
uv tool install gaze-py

# Or with pip
pip install gaze-py

Basic usage

# Analyse a source directory (CRAP will be null — no coverage provided)
gazepy analyze src/

# JSON output (default)
gazepy analyze src/ --format=json

# Human-readable text output (one line per function)
gazepy analyze src/ --format=text

# CRAP scoring — auto-runs pytest for coverage
gazepy crap src/

# CRAP scoring with a pre-generated coverage report
gazepy crap src/ --coverprofile coverage.json

# Scaffold OpenCode agent and command files into .opencode/
gazepy init

CRAP scoring with gazepy crap

CRAP scoring requires line coverage data. The crap command can collect coverage automatically by running pytest, or accept a pre-generated coverage.py JSON report:

# Auto-run pytest and collect coverage (requires pytest-cov)
gazepy crap src/

# Use a pre-generated coverage report (recommended in CI to avoid a double test run)
pytest --cov=your_package --cov-report=json:coverage.json
gazepy crap src/ --coverprofile coverage.json

When coverage is provided, the line_coverage and crap fields are populated in the output. When omitted, those fields are null (not 0.0) — null means "not measured", not "zero coverage". GazeCRAP and quadrant fields remain null until O1 ships.

The analyze command detects side effects only — it does not compute CRAP scores. Use gazepy crap for CRAP scoring.

Understanding the output

Each function in the output includes:

Field	Description
side_effects	List of detected observable side effects with type, tier, and classification
complexity	McCabe cyclomatic complexity
line_coverage	Fraction of lines covered (0.0–1.0), or null if not provided
crap	CRAP score (complexity² × (1 − coverage)³ + complexity), or null
gaze_crap	GazeCRAP score using contract coverage, or null (O1 deferred)
quadrant	Q1–Q4 classification based on CRAP and GazeCRAP, or null
fix_strategy	Recommended action: add_tests, decompose_and_test, or decompose
contract_coverage	Fraction of contractual effects covered by tests, or null

The summary section includes recommended_actions — up to 20 functions sorted by priority (add_tests → decompose_and_test → decompose) that exceed the CRAP threshold.

Current limitations

• GazeCRAP scoring deferred: The O1 quality/assertion mapping engine (which computes contract_coverage from test assertions) is not yet implemented. As a result, gaze_crap, contract_coverage, and quadrant are always null in this release. The fix_strategy field uses CRAP-only rules (Q3/add_assertions is unreachable without O1).
• Effect confidence range deferred: The effect_confidence_range field is present in the output schema (as null) but not yet computed.

Releasing

Releases are published to PyPI via GitHub Actions using trusted publishing (OIDC — no stored secrets).

One-time setup (already done)

1. PyPI trusted publisher: pypi.org → gaze-py project → Settings → Publishing → publisher configured for mpeter/gaze-py, workflow release.yml, environment pypi.
2. GitHub environment: repo Settings → Environments → pypi (optional approval gate).

Releasing a new version

1. Bump version in pyproject.toml and __version__ in src/gaze_py/__init__.py in a PR. Merge to main.
2. Go to GitHub Actions → Release → Run workflow.
3. Enter the tag matching the version (e.g. v0.3.0).
4. Approve the pypi environment gate if configured.
5. The workflow validates, tags, builds, and publishes automatically.