archithreat
Convert ArchiMate 3.x architecture models into threat-modeling artifacts, preserving logical trust zones, host containment, and connection semantics. Two output targets ship: IriusRisk-compatible draw.io and OWASP Threat Dragon v2 JSON. The codebase is structured so further targets slot in without rework.
Why
Threat-modeling tools that consume diagrams expect specific input formats (draw.io for IriusRisk, .tm7 for Microsoft TMT, JSON for OWASP Threat Dragon). None ingest ArchiMate directly. Organizations doing serious EA in ArchiMate (TOGAF, BiZZdesign, Sparx EA) have no path from authoritative architecture into their threat model except manual reconstruction. archithreat closes that gap.
Privacy by design
Architecture models for critical infrastructure describe attack surfaces and frequently cannot leave their owning organization. archithreat ships three surfaces, no hosted service:
- CLI — local conversion for engineers and CI pipelines.
- Browser app — static site (Pyodide); runs entirely in your browser, no upload.
- Self-hosted container — FastAPI image you run inside your trust zone.
Install (CLI)
pip install archithreat[cli]
archithreat convert input.xml output.drawio --target iriusrisk
archithreat convert input.xml output.json --target threatdragon
archithreat targets
Browser app
Open the published GitHub Pages site, drop your .xml in, pick a target from the dropdown, download the .drawio or .json. Nothing leaves your browser.
Self-hosted container
docker run --rm -p 8000:8000 ghcr.io/rondlite/archithreat:latest
# open http://localhost:8000
Documentation
- docs/concepts.md — modeling discipline behind the conversion
- docs/mapping-table.md — YAML schema + customization
- docs/patterns.md — supported patterns
- docs/limitations.md — known gaps and future work
- docs/self-hosting.md — Docker deployment
- docs/browser.md — browser app capabilities
- docs/privacy.md — what each surface does and does not see
- docs/targets.md — supported output targets
- docs/adding-a-target.md — contributor guide for new emitters
Status
v3.2.0. See CHANGELOG.md and ROADMAP.
License
Apache 2.0 — see LICENSE. For third-party / vendored components and their licenses (Pyodide, drawio viewer, HTMX, declared Python deps), see SBOM.md.
Metadata
Release files for archithreat 3.2.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 | |
|---|---|---|---|
| archithreat-3.2.0.tar.gz | 300.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| archithreat-3.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 367.3 kB
Release files / archithreat-3.2.0.tar.gz
| Download URL | archithreat-3.2.0.tar.gz |
|---|---|
| Size | 300.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db44ec4090cbe8587c73a90a67e3e103db8ad1c96c61293f8e7d721e499447c1
|
|
BLAKE2b-256 checksum How to use checksums |
84462c3e49e989ee07cf91c8ac3ee21ed9466a6c7021bec6e56a2023d1f8d80b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 3, 2026.
Transparency logRelease files / archithreat-3.2.0-py3-none-any.whl
| Download URL | archithreat-3.2.0-py3-none-any.whl |
|---|---|
| Size | 67.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3935c041fbf1ccd4f2bcfe05943d348eebe5f465a3e6212a61dd3772c41dd31f
|
|
BLAKE2b-256 checksum How to use checksums |
f842d0f5ac03cb8a637d8a3fe9c4ffcf0209fe7e4157c632fc8b87a568a0121d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 3, 2026.
Transparency log