Early Access
Python Package

Modern Cryptography

Replacing deprecated hashing and encryption algorithms with current best-practice equivalents.

Early Access: Until 2026-12-31

Back Overview Requirements

Cryptography in mgpy is not a marketing add-on. Signed offline activation, secret handling and supply-chain protection require modern primitives and clear key flows.

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 ....
  • MD5, SHA1 and hand-rolled encryption paths should not appear in new solutions.
  • Signatures, tokens and key material must be handled separately from debug and test artifacts.
  • Crypto decisions should be documented and re-checked against operational reality regularly.

Recommended mgpy workflow

  1. Inventory old hashing and signing paths and replace them in prioritized steps.
  2. Include keys and activation files in the security and release checks.
  3. Do not silently tolerate insecure legacy paths; remove them through explicit migration decisions.

Quick start

invoke security-scan
py -3.12 -m manifestguard license device-hash
py -3.12 -m manifestguard license status

Requirements

Columns
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.