Run, Radar, Run
Using run-radar-run
Requirements
- Python3.12+
- Docker (for the TWBYOR radar)
Running the Radar
Clone this repository and run:
$ ./run-radar-run
Or if you intend to see a specific radar directory, run:
$ ./run-radar-run -i tests/radar
Publishers
Publishers are the frameworks you can use to publish your tech radar.
As of early 2025, the publishers available are:
- Thoughtworks' Bring Your Own Radar
- Zalando Tech Radar
1 maintainer
Metadata
1 maintainer
Release files for run-radar-run 1.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 | |
|---|---|---|---|
| run_radar_run-1.0.0.tar.gz | 6.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| run_radar_run-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / run_radar_run-1.0.0.tar.gz
| Download URL | run_radar_run-1.0.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fff56e52fcf001e3b3c78cf209ce018975e1b6d61a6dac13f930e4d711c42add
|
|
BLAKE2b-256 checksum How to use checksums |
1f80705689e262af84cd710d25748b2f84d0517b31e50e33c6b415929f753857
|
| 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 23, 2026.
Transparency logRelease files / run_radar_run-1.0.0-py3-none-any.whl
| Download URL | run_radar_run-1.0.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f40b469279e978050a7d79fc3d602caeb2cab1b9a5a23cdfaf507eb4b4d4d05
|
|
BLAKE2b-256 checksum How to use checksums |
3d1702b3f098a9a55ebc4b9f34aa1c4f1a20f0e851c1d613ec6209d3fb931626
|
| 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 23, 2026.
Transparency log
