Python Package

Quality Regression Detection

Tracking quality trends over time and alerting on regressions across commits.

Early Access: Until 2026-12-31

Back Overview Requirements

Regression detection is the bridge between a single run and real maintenance. mgpy should preserve improvements and surface backslides early.

Key points

CLI: On Windows the examples use the recommended py -3.12 -m <module> ... form (for example py -3.12 -m manifestguard ...). On Linux/macOS this usually maps to python3.12 -m ....
Baseline comparison is more reliable than gut feeling after larger refactors.
Regressions can come from coverage, complexity, security or packaging and should be reviewed together.
A saved good state only matters when the team actually compares against it in daily work.

Recommended mgpy workflow

Save a clean reference point before bigger changes.
After the rewrite, compare intentionally instead of reading only the new run in isolation.
When deltas are negative, decide whether they represent a conscious trade-off or an accidental regression.

Quick start

py -3.12 -m manifestguard baseline --save-label pre-change
py -3.12 -m manifestguard check --extended
py -3.12 -m manifestguard baseline --compare pre-change

Requirements



Installation interpreter	Python 3.12 + pip	Recommended default path for installation and CLI calls.
Project target versions	Python 3.8 to 3.12	These are the project/runtime targets mgpy can analyze.
mgpy runtime	Validated on Python 3.10 to 3.13	The tool runtime itself is covered for this range.
CLI invocation	Windows: py -3.12 -m manifestguard	Linux/macOS usually maps to python3.12 -m manifestguard.
Runtime packages	tomlkit, click, pydantic, packaging, watchdog, PyNaCl, rfc8785	tomli is only added for Python below 3.11.
Offline / wheel install	Optional via pip --no-index or wheel	Useful for air-gapped or approved bundle distribution paths.