Antra
How it worksStar1Get Started
Star1
Antra
How it worksStar1Get Started
Star1
Documentation
  • Introduction
  • Installation
  • Quick start
  • Configuration basics
  • Monorepos
  • Trust boundaries
  • Findings and severity
  • Schema providers
  • Suppressions and baselines
  • antra init
  • antra scan
  • antra sync
  • antra doctor
  • antra baseline
  • antra trace
  • antra watch
  • antra fix
  • antra query
  • antra studio
  • Studio
  • Launching Studio
  • Reading the graph
  • Configuration reference
  • BG-001: Server-to-client leak
  • BG-002: Unvalidated input
  • BG-003: Opaque object pass
  • BG-004: Secret in markup
  • GitHub Actions
  • Introduction
  • Installation
  • Quick start
  • Configuration basics
  • Monorepos
  • Trust boundaries
  • Findings and severity
  • Schema providers
  • Suppressions and baselines
  • antra init
  • antra scan
  • antra sync
  • antra doctor
  • antra baseline
  • antra trace
  • antra watch
  • antra fix
  • antra query
  • antra studio
  • Studio
  • Launching Studio
  • Reading the graph
  • Configuration reference
  • BG-001: Server-to-client leak
  • BG-002: Unvalidated input
  • BG-003: Opaque object pass
  • BG-004: Secret in markup
  • GitHub Actions

antra sync

Refresh the static schema snapshot from your database, Prisma, or Supabase.

Re-reads your data layer and rewrites the schema snapshot that antra init created.

Usage

antra sync [path]

path is the Next.js app root and defaults to ..

When to run it

Run sync after a change that alters which fields exist or which of them are sensitive:

  • a migration added or renamed a column
  • a Prisma schema changed
  • a Supabase table gained a column

Without a fresh snapshot, a scan is judging your code against a stale picture of the schema, which is how you get both false positives and quiet misses.

Flags

sync takes no options beyond the optional path.

Previous
antra scan
Next
antra doctor
On this page
  • Usage
  • When to run it
  • Flags