Fail-Closed Gates
Deterministic gates — Bandit, Semgrep, Trivy, Gitleaks, Checkov and more — run in pinned Docker runners on every audit. A single P0 finding forces NO-GO. There is no --force flag.
v0.4.3 · Forge by Windmill
Forge audits every release against an 18-domain framework — 29 gates across Python, Node, Java and Flutter repos — scrubs secrets, and gates delivery through recorded admin approval. One repo or a whole campaign roster. Ships as both a CLI and a multi-tenant platform.
Why Forge
Three principles differentiate Forge from off-the-shelf SAST/DAST stacks. All three are load-bearing in regulated environments.
Deterministic gates — Bandit, Semgrep, Trivy, Gitleaks, Checkov and more — run in pinned Docker runners on every audit. A single P0 finding forces NO-GO. There is no --force flag.
Four enforcement layers: agent refuses locally, admin approves in-app, push-service ships with its own deploy key, git-host rejects pushes from anyone else. No single credential can ship code.
18-domain framework + 5-judge LLM panel. Append-only registry records every verdict with reproducibility headers. The same bar for every client; per-client configs layer in policy floors, never exceptions.
What gets checked
Deterministic gates run in pinned Docker runners; LLM lanes add a 5-judge review. Profiles are language-aware — Python, Node, Java and Flutter repos each get the gate set their stack warrants.
The deterministic Python baseline on every audit — Bandit SAST, pip-audit SCA, a coverage floor, and an SBOM.
Maintainability per language — Lizard complexity, ruff/vulture/pylint, deptry dependency hygiene, PMD for Java, dart analyze for Flutter, ESLint/jscpd/knip for Node — plus API-contract, architecture, IaC, observability and documentation gates.
SAST, SCA, container, IaC-security, secret-history, auth, encryption and security-logging gates — plus a phantom-dependency / slopsquatting check for hallucinated packages.
Row-level access-control enforcement and waiver hygiene — expired or over-long waivers are flagged, never silently honoured.
Prompt versioning, audit-log verification, an entitlement firewall and an adversarial test pack — the controls specific to AI-built and AI-operated systems.
How it works
Discover the project, scaffold .forge/, detect stack and project_kind.
Run the profile-aware gate set + 5-judge LLM panel; final verdict written to the registry.
Orphan worktree + 5-phase scrub (removals, renames, rewrites, sed, grep gate) under a default-deny allowlist.
Profile-dispatched build: DockerCompose, Flutter, or PureBuild — must pass before promote.
Annotated tag + SHA256 archive + dependency evidence; push command printed for the operator.
Two ways to run it
The same gate engine and the same verdict bar, whether you gate a single service or orchestrate a release across dozens of repos.
One repository, scaffolded once and gated on every release. Runs locally or in CI.
forge scan — discover the stack, scaffold .forge/forge audit — run the profile-aware gate set + judge panelforge release — scrub, stage, verify, tag — push stays gatedA whole roster of repositories audited and released together from one deliver folder.
forge campaign init — scaffold the deliver folder + rosterforge campaign audit — audit every repo, unified output treeforge campaign release — release the roster at one versionforge campaign status — one verdict table across all reposModules
One-shot discovery + manifest scaffolding. Recognises python, node, flutter, eval-harness, and java/Kotlin services.
Deterministic gates + LLM lanes (Claude or OpenAI) + 5-judge panel. Unified SARIF 2.1.0 report; evidence archived to the append-only registry per run.
Staged delivery branch, dependency evidence (SBOM where available), annotated tag, archive with SHA256.
Admin-only sign-off, tenant-scoped, append-only audit trail. Push-service polls and ships only after approved=true.
Industries
Meet the documentation and evidence bar regulators expect.
Prove non-bypass to auditors; separate duties by design.
HIPAA-minded release trails with tamper-evident approvals.
Supply-chain-safe releases for safety-critical software.
We'll stand up a demo tenant against a repo you pick. Under 30 minutes from SSO handshake to first audit.