Skip to main content

CBE — Cyber-Butler Enforcement gate

Who it is for: platform, security, and release engineers who need a deterministic gate between “CI passed” and “this artifact may ship”.

What it solves: CBE turns rule-pack manifests into an enforceable release gate: it validates the pack, runs providers, rejects disable/skip attempts, emits SARIF, and produces a machine-readable gate report plus a Release-body fragment. It is a sibling of CBS, CBP, and CBM, not a replacement for them.

How to start:

python -m pip install cbe-review
cbe --help
cbe validate-manifest --manifest rules.json \
  --package-type cbs --package-version v1.7.0

Important: pip install cbe installs a different project (Crossroads Bank for Enterprises). This project is distributed as cbe-review. Its import package and CLI are still cbe.

Install

python -m pip install cbe-review

Requires Python 3.10+. Runtime dependencies: jsonschema and pyyaml.

From a GitHub Release, use the attached cbe_review-0.1.1-py3-none-any.whl (or the sdist).

Quick start

# Validate a rule pack
cbe validate-manifest --manifest rules.json

# Run providers and write evidence
cbe run-provider --manifest rules.json --source-root . --out-dir out --all

# Enforce no-bypass rules
cbe enforce-no-bypass --manifest rules.json --source-root . \
  --package-type cbs --package-version v1.7.0 --workflows

# Build a symbol index / merge SARIF
cbe symbol-index --source-root . --out out/symbol-index.json
cbe emit-sarif --manifest rules.json --run-report out/run.json \
  --source-root . --out out/cbe.sarif

Exit codes: 0 PASS, 2 input/format error, 3 gate failure or SKIPPED_INFRA, 4 skip ratio > 20%.

What CBE checks

  • Rule-pack schema and semantics, including canonical manifest hash.
  • Provider execution and SARIF/JSON artifact validation.
  • No-bypass controls across config, source comments, environment, and GitHub Actions workflows.
  • Workflow gate-job reachability, including local reusable-workflow delegation.
  • CBE report identity, counts, skip ratio, and Release-body Section B.

Dynamic workflow expressions are not guessed. By default they are reported as UNVERIFIABLE_* warnings; use enforce-no-bypass --strict to turn the unverifiable conditions into exit 3.

Topics: release-gate, sarif, supply-chain, provenance, python.

Status and compatibility

CBE 0.1.0 is released on GitHub and PyPI (cbe-review==0.1.0). This tree is 0.1.1, adding Apache-2.0 licensing and complete package metadata.

0.1.0 metadata is immutable. PyPI metadata (license, classifiers, project URLs, author) cannot be changed after upload; the corrections in 0.1.1 take effect only in the new release. The 0.1.0 artifacts and v0.1.0 tag are unchanged.

License

Apache License 2.0. See LICENSE.

Development

python -m pip install -e ".[e2e]"
pytest
pytest tests/unit --cov=cbe --cov-fail-under=60

The CI matrix runs Ubuntu and Windows on Python 3.10. The gate covers unit coverage; E2E commands run in subprocesses and are not counted by coverage.

Metadata

Release files for cbe-review 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cbe-review 0.1.1
File Size Uploaded Provenance Actions
cbe_review-0.1.1.tar.gz 45.4 kB With provenance Details for cbe_review-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cbe-review 0.1.1
File Interpreter ABI Platform Actions
cbe_review-0.1.1-py3-none-any.whl Python 3 none any Details for cbe_review-0.1.1-py3-none-any.whl

Total release size: 99.6 kB

Release files / cbe_review-0.1.1.tar.gz

Download URL cbe_review-0.1.1.tar.gz
Size 45.4 kB
Tags Source
SHA-256 checksum
How to use checksums
768d2ea635e263b168871df2080537c0a6d84a316cfb34623240e54931bc4c96
BLAKE2b-256 checksum
How to use checksums
b34bc08027c28d17d0b568e3b62771e0360659f4227f6a334c110ef93ef50156
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 10, 2026.

Transparency log

Release files / cbe_review-0.1.1-py3-none-any.whl

Download URL cbe_review-0.1.1-py3-none-any.whl
Size 54.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b838e4366196933e043119614d982f5bebdf3cc9a3d382ce7a302b96fd882f58
BLAKE2b-256 checksum
How to use checksums
ea0fc0dfaf3522e42a11baac66ac544ca432b8df487a3d5579a2f154a4cc75f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 10, 2026.

Transparency log

Security for cbe-review 0.1.1

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cbe_review-0.1.1.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 Nov 10, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page