mipiti/Mipiti Verify

Verify security controls against Mipiti threat models in CI. Runs typed assertions against your codebase and reports results.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
model-idMipiti threat model ID (omit if using all)no""
allVerify all models in the workspacenofalse
api-keyMipiti API key (MIPITI_API_KEY)yes
base-urlAPI base URLnohttps://api.mipiti.io
tier2-providerAI provider for Tier 2 verification: openai, anthropic, or ollamano""
tier2-modelModel name (e.g. gpt-4o, claude-sonnet-4-5-20250514)no""
tier2-api-keyProvider API key (OpenAI or Anthropic)no""
project-rootProject root directoryno.
reverifyRe-verify all assertions, not just pending (default true)notrue
dry-runRun verifiers but don't submit resultsnofalse
concurrencyMax concurrent Tier 2 LLM callsno1
sigstore-tuf-urlCustom Sigstore TUF root URL for private deployments (default public sigstore.dev)no""
sigstore-trust-configPath to a pre-downloaded Sigstore ClientTrustConfig JSON (out-of-band snapshot, skips all TUF network fetches)no""
workspace-signing-keyPath to a PEM ECDSA P-256 private key for workspace-attested submission. Used when no OIDC token is available (e.g. self-hosted runners without id-token: write), or when signing-prefer=workspace. The matching public key must be registered on the Mipiti workspace.no""
signing-preferWhen both an OIDC token and a workspace key are available, prefer this signer ('sigstore' or 'workspace'). Default: sigstore.nosigstore
require-attestationFail the run when no attestation is produced (Sigstore or workspace-ECDSA). Default behaviour is to log a warning and submit unsigned when both signers are unavailable; with this flag, the runner exits non-zero. Set to 'true' for security-sensitive CI gates.nofalse
namedescription
content-hashSHA-256 content hash of verified assertions (sha256:<hex>). Use with actions/attest-build-provenance for Sigstore attestation.