hoolicy

README

Hoolicy

Understandable policy as code for repositories.

Hoolicy turns repeated repository, compliance, supply-chain, and product-quality checks into strict YAML policies. Simple rules stay simple. Complex structured rules use bounded CEL or a compile-time Go extension. hoolicy check never downloads policy code and never executes scripts from a policy pack.

Quick start

Install a release binary, use the container, or build with Go 1.26+:

go install github.com/openhoo/hoolicy/cmd/hoolicy@v0.2.1
# or: docker run --rm --user "$(id -u):$(id -g)" -v "$PWD:/work:ro" -w /work ghcr.io/openhoo/hoolicy:v0.2.1 check

For rootless Podman, add --userns=keep-id. Mapping the caller UID lets the non-root image read private repository files without weakening their host permissions.

Create a useful starter policy:

hoolicy init --project my-service
hoolicy check

Default standard profile checks repository documentation, licensing, vulnerability reporting, Git naming, and artifact sources. --profile strict also requires literal container images to use sha256 digests. --profile empty creates only the strict configuration skeleton.

Small rules look small

version: 1
project: payments-api
failOn: error
rules:
  - id: repository.security-policy
    title: Repository documents vulnerability reporting
    description: Requires SECURITY.md at repository root.
    rationale: A private reporting path reduces unsafe public disclosure.
    remediation: Add reviewed reporting and supported-version instructions.
    severity: error
    kind: files
    files: [SECURITY.md]
    spec:
      mode: require
      message: SECURITY.md is required

Every rule must explain what it checks, why it matters, and how to remediate it. Hoolicy rejects unknown fields, duplicate YAML keys, invalid rule specs, duplicate rule IDs, and unsafe paths.

Commands

hoolicy init       Create standard, strict, or empty starter policy
hoolicy validate   Compile configuration, packs, regexes, and CEL
hoolicy check      Evaluate policies offline
hoolicy fix        Preview safe fixes; --apply writes reviewed changes
hoolicy list       List active rules and their source
hoolicy explain    Show rationale, remediation, and control mappings
hoolicy test       Run pass and fail fixtures for policy packs
hoolicy baseline   Preview or apply reviewed finding baselines
hoolicy doctor     Diagnose policy, Git, lock, and CI inputs
hoolicy report     Compare JSON policy reports by fingerprints and digests
hoolicy evidence   Create or verify decision evidence and attestations
hoolicy waiver     Preview or apply an exact finding-bound waiver
hoolicy inventory  Emit workspace policy and ownership inventory
hoolicy serve      Run the optional loopback, GET-only reuse service
hoolicy migrate    Preview or apply supported format migrations
hoolicy pack       Add, update, or verify vendored packs

Reports: human text, JSON, SARIF 2.1.0, JUnit XML, GitHub step summaries, and GitLab Code Quality. Exit codes: 0 passed, 1 a new policy finding met failOn, 2 configuration or execution error.

Existing repositories can adopt policy without hiding debt. hoolicy baseline create previews an exact, digest-bound baseline; --apply writes it. Full checks continue to report existing findings while blocking only new or materially changed findings. See baseline adoption and CI.

Standard packs

• packs/repository: Git branch, commit, and merge-request naming.
• packs/supply-chain: approved npm, NuGet, and OCI sources plus expiring security exceptions.
• packs/product-quality: translation-key parity and semantic Gherkin coverage.
• packs/ci-workflow-security: structured GitHub Actions and GitLab CI trust boundaries.
• packs/artifact-evidence: pinned SARIF, SBOM, test, and provenance evidence.
• packs/dependency-governance: lock, source, local-reference, and license governance.
• packs/deployment-invariants: parameterized Kubernetes, Compose, and Terraform plan invariants.
• packs/api-contract-hygiene: experimental OpenAPI consumption-evidence comparison.

Use this repository as a versioned remote pack source:

packs:
  - name: repository
    git: https://github.com/openhoo/hoolicy.git
    ref: v0.2.1
    subdir: packs/repository
    with:
      branch_pattern: '^(feat|fix|chore)/[a-z0-9]+(?:-[a-z0-9]+)*$'
      commit_pattern: '^(feat|fix|chore)(\([a-z0-9-]+\))?!?: .+$'
      merge_request_title_pattern: '^(Draft: )?(feat|fix|chore)(\([a-z0-9-]+\))?!?: .+$'
      allowed_branches: [main]
      merge_request_title_maximum: 100

Run hoolicy pack update repository once. It resolves the Git ref, vendors the exact pack, and writes hoolicy.lock with commit and content digest. Later validate and check operate offline and fail on tampering.

Guardrails for guardrails

• No runtime plugins, shell commands, network calls, or foreign code from YAML.
• Checks retain Git-aware file discovery and metadata through a read-only built-in fallback when the git executable is unavailable.
• CEL has static checking and a configurable cost cap, hard-limited to 1,000,000.
• Waivers require owner, HTTPS ticket, meaningful reason, narrow scope, creation date, and expiry within 90 days.
• Safe fixes are hash-bound, refuse dirty targets and symlinks, show a diff first, and require --apply.
• Pack tests require at least one passing and one failing fixture for every published rule.

Start with rule authoring, policy packs, decision evidence, monorepo workspaces, architecture and threat model, compatibility, or recovery. Product intent and non-goals live in the roadmap; repository implementation and remaining external gates are tracked separately in roadmap status. A generic repository-policy example lives in examples/repository-policy.

Project status

Latest published release remains the version in VERSION. Current development source contains the roadmap implementation through the proposed v1 contracts, but it is not a v1 release until independent security review, remote CI, tagged publication, and artifact verification complete. Configuration version 1 is strict; the compile-time Go SDK may still evolve before v1.0.0.

Commits use Conventional Commits and are checked by Hooversion. After CI passes on main, feat commits publish a minor release, fix and perf commits publish a patch release, and breaking changes publish a major release. Hooversion updates VERSION and CHANGELOG.md, creates the tag and GitHub release, then the release workflow attaches signed binaries, an SPDX SBOM, provenance, and a signed multi-platform GHCR image.

Apache-2.0. See CONTRIBUTING.md and SECURITY.md.

Documentation

Overview

Package hoolicy exposes the compile-time extension entry point for custom Hoolicy binaries. Standard CLI users should install cmd/hoolicy instead.

Index

• func NewRegistry() (*sdk.Registry, error)
• func Run(ctx context.Context, args []string, info BuildInfo, register RegisterFunc) int
• type BuildInfo
• type RegisterFunc

Functions

func NewRegistry

func NewRegistry() (*sdk.Registry, error)

func Run

func Run(ctx context.Context, args []string, info BuildInfo, register RegisterFunc) int

Types

type BuildInfo

type BuildInfo struct {
	Version string `json:"version"`
	Commit  string `json:"commit"`
	Date    string `json:"date"`
}

type RegisterFunc

type RegisterFunc func(*sdk.Registry) error