Frontier Infra
host-neutral core · host-specific adapters

Put the standards to work.

The Frontier SDK turns governance patterns into versioned, executable checks. Plugins make that engine natural to use inside a coding harness without moving the scoring rules into prompts.

SDK

Frontier SDK

A model- and harness-neutral SDK for deterministic repository scoring, Git-bound evidence packets, and optional signed AAR receipts. Versioned code owns the scoring semantics so results remain comparable across model and host updates.

@frontier-infra/audit@0.1.0-rc.2

Release candidate · public source

View the SDK on GitHub →

One engine, multiple harnesses

The SDK owns deterministic scoring, evidence commitments, and receipt verification. Each adapter owns discovery, permission-aware bootstrap, and the conventions of its host. A host update can change how the workflow is invoked without silently changing what a score means.

Codex

Frontier Audit

Inspects for the pinned SDK, asks before installing executable code, verifies the approved integrity chain, then runs the SDK-owned audit instead of merely returning commands.

Release candidate · public source · marketplace publication pending

View Codex adapter source →

Claude Code

Frontier Audit

The planned Claude Code adapter will use the same SDK, scorer lock, evidence format, and trust disclosures. No separate prompt-defined scoring semantics and no public marketplace claim yet.

Adapter in preparation · no public marketplace listing yet

Track Claude adapter progress →

What the audit actually does

  1. Locks the procedure. The record names the exact SDK version and scorer-policy hash.
  2. Scores the repository. Versioned code runs the canonical static conformance kit against the target Git state.
  3. Commits the evidence. JSON and Markdown output bind the verdict to the repository commit and dirty-tree state.
  4. Optionally signs a receipt. A local signing key can issue an AAR that is immediately verified offline against the supplied DID document.

Questions, release issues, or sensitive reports? Start at Support. The local execution and data boundaries are documented in Privacy and Terms.