Hexastack Tools (packages/hexastack_tools)
Developer tooling, repository governance, code-scanning analysis, and CI automation suite for the Hexastack monorepo.
📖 Complete Documentation & Usage
For full CLI usage instructions and command examples, see the canonical USAGE Guide or the online developer documentation.
🏛️ Architectural Intent
hexastack-tools strictly dogfoods Hexastack's own hexagonal architecture with:
domain/: Pure data contracts (PrSummary,CheckRunFinding,ReviewThread,OutputFormat).ports/: Decoupled port interfaces (GitHubApiPort).adapters/: REST/GraphQL HTTP adapters (GitHubHttpAdapter) and multi-format presenters (pr.py,checks.py,security.py).commands/: Clean Typer CLI entrypoints.utils/: Shared monorepo workspace discovery and package graph resolvers.
⚙️ Output Presentation Modes
All CLI commands support multi-format presenters:
auto(default): Renders interactive Rich tables/panels if connected to a terminal TTY, or automatically switches to plain TSV when output is piped to tools likegrep,awk,cut, orxargs.rich: Colorized ANSI dashboards with status icons and panels.json: Structured JSON payload for CI integration or agent tooling.plain: Clean, newline- and tab-delimited (TSV) stream.
🛠️ Quick Command Reference
| Command | Purpose |
|---|---|
uv run gh-pr-examine [pr] |
Full PR dashboard inspecting checks, review threads, failed CI logs, and conflicts. |
uv run gh-pr-examine runs [branch] |
Lists recent workflow runs for a branch. |
uv run gh-checks [pr/ref] |
Detailed status checks inspector. |
uv run gh-security [pr] |
Review comments and bot discussion thread auditor. |
uv run gh-code-scanning |
CodeQL SAST security alerts browser. |
uv run check-test-parity |
Validates 1:1 mirroring between src/ and tests/unit/. |
uv run check-all-statements |
Validates __all__ alphabetical sorting. |
uv run fix-all-statements |
Automatically sorts and alphabetizes __all__. |
uv run check-extras-parity |
Audits subpackage optional extras forwarding into umbrella packaging. |
uv run deps-audit |
Unified dependency runner (deptry + extras parity audit across workspace). |
uv run import-linter-run |
Validates package and hexagonal architecture layer boundaries. |
| uv run pypi-build | Builds sdist and wheel packages across workspace. |
| uv run pypi-check | Verifies build metadata and checks for PyPI release collisions. |
| uv run codeql-scan | Runs local SARIF CodeQL SAST security scan. |
For detailed syntax and flags, see USAGE.md.
Metadata
Release files for hexastack-tools 0.4.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 | |
|---|---|---|---|---|
| hexastack_tools-0.4.0.tar.gz | 68.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hexastack_tools-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 159.7 kB
Release files / hexastack_tools-0.4.0.tar.gz
| Download URL | hexastack_tools-0.4.0.tar.gz |
|---|---|
| Size | 68.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aaa740d7e84e0d2dfb5dd57dd4feb2f0adee16bfa1905b0ea5b67f94a3e53765
|
|
BLAKE2b-256 checksum How to use checksums |
22260659c3e28dd9306fadef3ae99ca8e1258a9d8558f79283f1e46248b55a1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / hexastack_tools-0.4.0-py3-none-any.whl
| Download URL | hexastack_tools-0.4.0-py3-none-any.whl |
|---|---|
| Size | 91.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39a12a4274cca184b9d1024dcd8a3259fe6b3b98cd02c9d06f13477fdb736b47
|
|
BLAKE2b-256 checksum How to use checksums |
94838a486e9ba9c19645dfc47f7cfdd75b8fd7a3685f90ec13a3ca0e729700ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for hexastack-tools 0.4.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.