Stratum is now BakeX
This package has been renamed. Install bakex instead.
pip install bakex
stratumoss is no longer developed. Everything that was Stratum lives on as BakeX, built by
the same people, in the open, under Apache-2.0.
What changed
| Was | Now |
|---|---|
pip install stratumoss |
pip install bakex |
import stratum |
import bakex |
STRATUM_* environment variables |
BAKEX_* |
stratum_version: in a blueprint |
bakex_version: |
github.com/StratumOSS/Stratum |
github.com/invicton/bakex |
Installing this package pulls in bakex for you, so nothing breaks — but import stratum
will raise with a pointer to the new name. Update your imports and depend on bakex
directly.
Why the rename
"Stratum" is a common word and collided with existing projects, including an unrelated
stratum package on PyPI. The tool is now BakeX: you bake a declarative blueprint into
a rigid, ready-to-deploy golden image. It is published under the Invicton org.
This happened pre-launch, at v0.6.0. The full rationale is in the changelog.
What BakeX does
Describe a hardened OS in one YAML blueprint; BakeX builds the CIS/STIG-benchmarked golden image on any cloud — or locally on KVM — and hands you the compliance evidence.
bakex validate blueprints/ubuntu/22.04/cis-l1-aws.yaml
bakex build blueprints/ubuntu/22.04/cis-l1-aws.yaml
Provision → harden with Ansible-Lockdown → scan with OpenSCAP → snapshot → tear down. You get a golden image, an A–F grade, and a SARIF report.
- Repository: https://github.com/invicton/bakex
- Blueprint library: https://github.com/invicton/bakex/tree/main/blueprints
- Blueprint JSON Schema: https://github.com/invicton/bakex/blob/main/docs/schema/hardening-blueprint.schema.json
- Changelog: https://github.com/invicton/bakex/blob/main/CHANGELOG.md
Contributions are welcome — the blueprint library is deliberately pure YAML, and there are good first issues open for new OS/provider combinations.
Metadata
Release files for stratumoss 0.6.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 | |
|---|---|---|---|
| stratumoss-0.6.0.tar.gz | 3.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stratumoss-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / stratumoss-0.6.0.tar.gz
| Download URL | stratumoss-0.6.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
471054026fd1386fd906a32d3d0f7a6353007a8cb3f2dde75ee165cb42dd1f36
|
|
BLAKE2b-256 checksum How to use checksums |
e09c6c74cc6f217e89c01bc2d25e5edd5bbff76a3d041d73905c993c7eba5ef3
|
| 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 26, 2026.
Transparency logRelease files / stratumoss-0.6.0-py3-none-any.whl
| Download URL | stratumoss-0.6.0-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0d4aee5cbef3b5c92563f3cbf83ae2cf735e25fdef9da9d33f39df7dd48a19c9
|
|
BLAKE2b-256 checksum How to use checksums |
de0974e12961bc0293a309f1f6b74e654ee3014c3418ac0e1cd3f66a112dcbf6
|
| 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 26, 2026.
Transparency log