Verify, secure, and ship AI‑generated code.

• ✓No telemetry, ever
• ✓Runs locally
• ✓Deterministic core
• ✓Signed self-update
• ✓Never runs your code
• ✓Apache-2.0

1. 01

   Install

   $curl -fsSL https://getdev.ai/install.sh | sh

   One static binary, no runtime and no account. On Windows: irm https://getdev.ai/install.ps1 | iex — or use a package manager below.

2. 02

   Set up your project

   $getdev init

   Writes .getdev.toml and offers a pre-commit hook plus an agent-context block. Add --yes to accept sensible defaults without prompts.

3. 03

   Get your Ship Score

   $getdev check

   One deterministic 0–100 score with ranked, explainable findings across real, audit, review, and secrets — from a single scan pass.

4. 04

   Fix the secrets

   $getdev env --write

   Moves hardcoded secrets to .env, rewrites the references, and patches .gitignore. Values are shown masked and never printed.

5. 05

   Checkpoint before big changes

   $getdev snap -m "before refactor"

   Restore in one second with getdev back when the agent goes sideways. Checkpoints hide in git — your branches, history, and stash are untouched.

6. 06

   Pre-flight for deploy

   $getdev ship --write

   Generates a Dockerfile and a deploy checklist and validates your env. getdev never runs your code unless you explicitly pass --run-build.

In CI: getdev check --json --fail-on high — exit non-zero when anything at or above your threshold is found.

getdev is the verification step an agent can run on its own output. It is deterministic, keyless, and machine-readable — drop it into the edit → check → fix loop and gate on the exit code. If your agent installs and runs tools for you, point it at getdev.

After editing code, run `getdev check --json --fail-on high`.
Fix every finding at or above the threshold, then re-run until it exits 0.
Secrets: run `getdev env --write`. Checkpoint risky edits: `getdev snap` / `getdev back`.

machine-readable summary: getdev.ai/llms.txt

• getdev check

  Run everything, get one Ship Score 0–100

• getdev real

  Verify that packages, APIs, and model strings actually exist (anti-slopsquatting)

• getdev audit

  Security scan tuned to AI-generated failure patterns

• getdev review

  Diff analysis: dead code, duplicate helpers, debug leftovers

• getdev env

  Extract hardcoded secrets to .env and rewrite the references

• getdev snap / back

  One-command checkpoints and one-second restore (hidden in git underneath)

• getdev ship

  Pre-flight: Dockerfile generation, env validation, deploy checklist

• getdev init

  First-run setup: write .getdev.toml, offer a pre-commit hook and agent-context block

• getdev update

  Signed self-update from GitHub Releases — SHA-256 checksum + cosign, atomic swap

• getdev doctor

  Self-diagnostics: version, cache, registry reachability, config validity

The privacy promise is mechanically enforced, not just asserted: two CI gates fail the build if a second network client or an LLM SDK enters the tree, or if a network call appears outside the sanctioned registry and self-update paths. Full threat model on GitHub.