Shipwright
Shipwright is two things that share one repo:
- an installable, import-light Python library of shared dev-tooling runtime —
shipwright_kit.design(severity tiers + accessible output),shipwright_kit.eval(detection-quality eval harness),shipwright_kit.security(a security pack); - an AI-agent-operated development framework — reusable CI/CD, a Copier scaffolder, quality gates, and bundled agent skills + personas — that dogfoods the library and the gates it hands to the projects built with it.
The library is consumed today by two real tools: barb and sift both import
shipwright_kit.eval to run their detection-quality gates.
Install
The bare name shipwright belongs to an unrelated project on PyPI, so the
published distribution is shipwright-kit and the import name is
shipwright_kit.
uv pip install "shipwright-kit>=0.7,<0.8"
# then: import shipwright_kit
[!NOTE] Do not
pip install shipwrightfrom PyPI — that is a different, unrelated package. The correct dist name isshipwright-kit.
The security pack needs no extra — it ships with the base install and registers
through the shipwright_kit.packs entry point.
Library quickstart
Run an eval gate — score a classifier against a labeled corpus and fail if it misses a floor (the exact pattern barb and sift use):
from shipwright_kit.eval import Sample, evaluate, gate
corpus = [Sample("phish-login", "phishing"),
Sample("example.com", "benign"),
Sample("secure-phish", "phishing")]
result = evaluate(
lambda text: "phishing" if "phish" in text else "benign",
corpus,
positive_pred=lambda pred: pred == "phishing",
positive_expected=lambda label: label == "phishing",
)
print(result.precision, result.recall) # 1.0 1.0
gate(result, min_precision=1.0, min_recall=0.9) # raises EvalGateError if below
Use the shared severity tiers — one generic scale tools map their own verdicts onto, with accessible (Unicode-or-ASCII) labels:
from shipwright_kit.design import Severity, tier_label
Severity.OK, Severity.INFO, Severity.NOTICE, Severity.WARN, Severity.CRITICAL # IntEnum 0..4
print(tier_label(Severity.CRITICAL)) # ✗ CRITICAL
print(tier_label(Severity.OK)) # ✓ OK
import shipwright_kit pulls in no rich or pyfiglet — the heavy deps load lazily only
when you actually render. Full API: docs/library.md.
The framework
The repo contains no project code. Projects stay their own Git repositories and
their own packages; locally you clone each into the gitignored projects/
directory, where a uv workspace ties them together for
development:
shipwright/
├─ shipwright_kit/ # the importable library (design / eval / security)
├─ tooling/ruff-base.toml # single source of truth for lint rules
├─ templates/ # Copier scaffolder (python-cli) + release config
├─ skills/ · personas/ # the agent operating layer (scaffold, onboard, review …)
├─ .github/workflows/ # reusable python-ci.yml + python-release.yml (SHA-pinned)
└─ projects/ # GITIGNORED, local-only — your projects plug in here
Work is promoted through gates; failing a rung blocks promotion:
commit → lint + unit (auto) → build → dogfood + eval (auto) →
QM gate (manual) → beta sign-off (manual) → release
The reusable CI/CD that wires these gates, the Copier scaffolder (templates/), and
the agent skills (skills/) and personas (personas/) all ship now. This repo runs
the exact gates it gives the projects built with it.
Framework quickstart
Requires Python 3.11+, uv, and just.
uv sync --dev # create the dev environment
uv run pre-commit install # install the local gate
just lint # ruff check + format-check
just test # pytest
The local pre-commit gate runs the same lint/format/secret checks as CI; add
just test (and uv build) for the test and build rungs CI also enforces.
Docs
- docs/library.md — per-module API reference (design / eval / security)
- docs/release-policy.md — SemVer + release policy
- docs/ci-cd.md — the reusable CI/CD workflows
- CHANGELOG.md
Security
Report vulnerabilities privately via GitHub's private vulnerability reporting (repo Security tab → Report a vulnerability). See SECURITY.md.
Author
Christian Huhn — building security tooling for SOC/DFIR workflows.
- GitHub: @duathron
- LinkedIn: Christian Huhn
License
MIT © 2026 Christian Huhn
Metadata
Release files for shipwright-kit 0.12.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 |
|---|---|---|---|---|
| shipwright_kit-0.12.0.tar.gz | 32.4 kB | With provenance | Details for shipwright_kit-0.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| shipwright_kit-0.12.0-py3-none-any.whl | Python 3 | none | any | Details for shipwright_kit-0.12.0-py3-none-any.whl |
Total release size: 60.6 kB
Release files / shipwright_kit-0.12.0.tar.gz
| Download URL | shipwright_kit-0.12.0.tar.gz |
|---|---|
| Size | 32.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b1ba00849527651ba9609ff9c77fc8328ede77ba7b1d8c5cb5ad829295fab3c
|
|
BLAKE2b-256 checksum How to use checksums |
577586a9fb86bd2f5912fdb76a13aec151906d13dca4a07f86e6ccd9f27f89f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 5, 2026.
Transparency logRelease files / shipwright_kit-0.12.0-py3-none-any.whl
| Download URL | shipwright_kit-0.12.0-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28e5c1a7aadfdabc852635ad5e52d1ce11117ea8c42b7eb9d4ad4be1989d0fe2
|
|
BLAKE2b-256 checksum How to use checksums |
7c59392c9fffe9d4d5a0f13454af6fe0d95972113846174db55b4e0819cdbd05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 5, 2026.
Transparency logSecurity for shipwright-kit 0.12.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for shipwright_kit-0.12.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 Jul 5, 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.