Manifest & packaging validation
Check pyproject/setup/requirements consistency and catch common packaging pitfalls before release.
Check pyproject/setup/requirements consistency and catch common packaging pitfalls before release.
Detect broken script targets, missing dependencies, and version conflicts in a single run.
Apply package allow/block rules and version constraints from plain configuration.
Add extra quality signals such as complexity, duplication, dummy code, and coverage-related metrics.
Write machine-readable reports and assess SBOM and license completeness. SPDX and CycloneDX are standard formats for these dependency inventories.
Preview supported fixes first, then let ManifestGuard write only registered supported patches after creating a workspace snapshot and per-file backups where your license allows it.
In the age of AI, programming sounds easy — until a module quietly grows to 4,000–7,000 lines, duplication creeps in, and forgotten dummy / placeholder code piles up. Then every fix takes longer, and the risk increases that an AI ‘simplifies’ by removing tested code paths — you notice it too late, and the day is gone.
ManifestGuard is my senior-engineer quality radar for Python projects: it scans structure, packaging, dependencies and policy rules, flags risks (SBOM/compliance gaps included), and shows what to fix — without sugarcoating.
Goal: clarity, not punishment. One command — and you know how healthy your project really is.
ManifestGuard Python is a CLI quality gate for Python repositories. It helps teams keep code quality measurable and repeatable across local development and CI pipelines.
manifestguard dashboard remains the baseline TUI workflow surfacepip; on Windows typically via py -3.12, on Linux/macOS typically via python3.12.pip installation pulls in the required runtime packages automatically: tomlkit, click, pydantic, packaging, watchdog, PyNaCl, and rfc8785; only Python versions below 3.11 additionally require tomli.py -3.12 -m pip install --user manifestguard; pin a fixed release with py -3.12 -m pip install --user "manifestguard==<VERSION>"./login and then move to /license/activate.py -3.12 -m manifestguard license device-hash, then copy the activation token returned by the portal.py -3.12 -m manifestguard license activate <TOKEN> and verify with py -3.12 -m manifestguard license status; the same token can later be reused in MGVS.Run checks locally before commit, then enforce the same criteria in CI. MGPY is designed for deterministic test behavior and unattended execution. CLI commands and machine-readable output make it suitable for release gates and team policy checks. A dedicated refactoring rules manifest keeps AI-assisted refactor guidance explicit and repeatable.
Goal: clarity, not punishment. One command gives a concrete quality status you can act on.
|
Manifest & packaging validation
|
✓
|
✓
|
✓
|
✓
|
|
Entry point consistency checks
|
✓
|
✓
|
✓
|
✓
|
|
Dependency analysis
|
✓
|
✓
|
✓
|
✓
|
|
Custom validation rules
|
–
|
✓
|
✓
|
✓
|
|
Extended analysis
|
–
|
✓
|
✓
|
✓
|
|
QuickFix suggestions
|
–
|
✓
|
✓
|
✓
|
|
QuickFix apply (supported findings + backup)
|
–
|
–
|
✓
|
✓
|
Early Access (until 2026-12-31)
Applies to the purchased version incl. all updates for 1 year from the purchase date.