Modwire
Your architecture already has rules. Modwire makes them enforceable.
Modwire turns intended boundaries into executable checks across Python, PHP, TypeScript, Java, and Ruby. When a dependency points backward, code crosses a boundary, a cycle appears, or the source layout drifts, Modwire reports the violation before the architecture becomes tribal knowledge.
Polyglot architecture checks, one model.
Modwire favours systems whose source tree makes bounded contexts, features or modules, and layers visible. Glob patterns map that convention onto a real repository. Boundary, dependency flow, cycle, re-entry, and shape checks keep it consistent as the system changes.
Installation
Modwire requires Python 3.12 or newer.
python -m pip install modwire
Quickstart
Create the project-local configuration, then run the reports for each language in the repository:
modwire init
modwire report --language python --summary
modwire report --language typescript --summary
modwire report --language php --summary
modwire report --language java --summary
modwire report --language ruby --summary
Each report run selects one language. The architecture vocabulary and rules stay the same across all five.
The supported Python interface is exported by modwire.application:
from modwire.application import ModwireApplication, ScanPolicy
application = ModwireApplication.create()
code_map = application.generate_queryable_map(
"python",
".",
ScanPolicy(excluded_patterns=(".git/**", ".venv/**")),
)
Documentation
- Documentation entrance
- Tutorials
- How-to guides
- Explanation
- Architecture
- Technical reference
- Language support and limits
- Recorded evidence
- Contributing
The documentation site covers the complete first workflow, configuration, caching, implementation manifests, failure contracts, language capability differences, recorded extraction evidence, and the supported Python surface.
Development
uv sync --all-groups --locked
make host-check
Build the documentation alone with make docs-check. Generated HTML is written to
docs/_build/html and remains outside source control.
Report defects and documentation gaps through the Modwire issue tracker.
Metadata
Release files for modwire 13.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| modwire-13.0.0.tar.gz | 4.5 MB | With provenance | Details for modwire-13.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| modwire-13.0.0-py3-none-any.whl | Python 3 | none | any | Details for modwire-13.0.0-py3-none-any.whl |
Total release size: 9.0 MB
Release files / modwire-13.0.0.tar.gz
| Download URL | modwire-13.0.0.tar.gz |
|---|---|
| Size | 4.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e29ea1189da9f74e9dce52c8df74ad19535861e30064d44079082ce18729503d
|
|
BLAKE2b-256 checksum How to use checksums |
3d296474074aa16f4188ae792737a7016974ffa047cf2ec755e48af37bd138dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logRelease files / modwire-13.0.0-py3-none-any.whl
| Download URL | modwire-13.0.0-py3-none-any.whl |
|---|---|
| Size | 4.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f4eb04f8868c095511df9fb37e45296c5509835f75747a2ede56a86c50a9b2b
|
|
BLAKE2b-256 checksum How to use checksums |
07f10504a42962584a0f9dd2ff5589fbe63cbb9907ad8f8feea9a2a68df584aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for modwire 13.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for modwire-13.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.