Trend Analysis

For mgpy, trends prove whether improvements hold or whether erosion starts early. Individual good runs do not replace historical visibility.

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 ....
• Weekly aggregates, baselines and history entries make quality changes tangible.
• Missing coverage data must be interpreted as a gap rather than an artificial zero.
• Trend views become especially valuable after multiple releases or refactor series.

Recommended mgpy workflow

1. Write reports and history entries regularly so enough comparison points exist.
2. Map visible degradations back to specific commits, releases or rule changes.
3. Read charts with context: a measurement gap is not the same as real quality improvement.

Quick start

py -3.12 -m manifestguard baseline --list
py -3.12 -m manifestguard export-metrics --output metrics.json
py -3.12 -m manifestguard check --extended --report .manifestguard/manifestguard-report.json