Skip to main content

🚀 Beta: All Pro and Team features are free. Install on GitHub →

Enforcement status

See where your posture reports — and where it prevents.

The cross-layer status surface gives an honest picture of the enforcement posture your configuration currently exposes.

What status reports

coderifts status is a read-only cross-layer enforcement report for Runtime, Merge, Deploy, and Content. It prints the statuses the endpoint measured: no GitHub writes and no branch-protection changes.

REPORTS

The result is visible while merge or deploy can still proceed.

PREVENTS

The action physically cannot proceed on that path.

coderifts status owner/repo
coderifts status --repo owner/repo --json

What enforce does

coderifts enforce closes enforcement gaps by chaining existing setup commands: Merge → setup-required-check; Runtime → hook install (apply only) plus agent-guard guidance; Deploy → deploy-gate CD-step guidance; Content → guidance only.

Dry-run by default

--apply is required to mutate. The command does not silently flip enforcement, does not bypass underlying command safety, does not label Runtime or Content as server ENFORCING, and does not upgrade UNKNOWN.

coderifts enforce owner/repo
coderifts enforce --repo owner/repo --apply

The reporting-to-enforcement bridge

status shows the posture the endpoint measured. enforce is the dry-run-first setup path for closing gaps. The gates enforce; these commands surface and configure the posture.

Honest bound

Status reflects configuration, not a guarantee. A layer shown as preventing depends on repository and host configuration. Prevention holds inside the wired boundary; an unwired surface can be bypassed.