Codve - Independent Code Verification

What Codve CI does

When a PR opens (or updates), Codve CI:

Collects the files to verify (optionally changed files only).
Runs Codve verification using either your locked spec or a preset.
Produces a CI report: pass/fail status, top findings, counterexamples (when available), and coverage status.
Optionally blocks merges via GitHub branch protection (turning the check into a true merge gate).

Two ways to use it

1) Spec mode (best for regression prevention)

If you’ve locked a spec in Spec Hub, Codve CI verifies every PR against that contract. If a rule breaks, the PR fails. This is the most reliable way to prevent regressions as your codebase evolves.

2) Preset mode (no specs required)

Don’t have specs yet? Start with a preset (like basic) to get value immediately — no rule writing, no spec creation, just verification.

Honest coverage (no false confidence)

Automated checks can be dangerously optimistic. Codve CI reports coverage so “green” never means “we guessed.”

Full: all targeted files analyzed
Partial: some files analyzed, some skipped
None: no files analyzed (tool/parse errors, etc.) — clearly shown in the report

Why this matters

If a file can’t be analyzed, Codve marks it as skipped with a reason. That’s more honest than silently passing.

Setup in minutes

In your GitHub repo:

Add your Codve API key as a GitHub secret.
Create a .codve.yml config.
Add the GitHub workflow file and require the check in branch protection rules.

Example: Preset mode

version: 1
preset: "basic"
paths:
  - "src/**/*.ts"
settings:
  failOn: error
  threshold: 0.8
  timeout: 300

Example: GitHub workflow

name: Codve Verification
on: [pull_request]

jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: codve/verify-action@v1
        with:
          api-key: ${{ secrets.CODVE_API_KEY }}
          config: .codve.yml

Tip

Start with preset mode, then move to spec mode later when you want strict regression guarantees.

Built for the free tier (and your infra)

We optimized CI runs to keep storage and traffic under control:

Payload limits (max files / max size)
We store metadata and hashes — not file contents
Findings are capped and long strings are truncated
Retention policy: older runs expire automatically

What’s next

Cleaner GitHub step summaries
Optional PR comment bot (show failing inputs directly in the PR)
More presets (security hygiene, null-safety, strict)
Smoother “Paste & Verify” onboarding for non-dev builders

Codve CI is Live: Turn Specs (or Presets) Into a Merge Gate