Blast radius
Every place in your code that depends on the schema being changed. Sieve surfaces these so you don't deploy a migration that breaks a system you forgot existed.
What we scan
- Application code that references the changed model, table, or column — across TypeScript, JavaScript, Python, Go, Ruby, and Java.
- Raw SQL fragments embedded in your code (template strings, query builders).
- OpenAPI specs and tRPC procedures that expose the affected fields.
- Tests that assert on the affected columns.
How it groups results
References are grouped by domain — auth, billing, admin, public API, analytics — so reviewers can immediately see the surface area. Each group is collapsible and links back to the exact line in your repo.
What it doesn't cover (yet)
- Other repositories that share the database (cross-repo scan is on the 2026 roadmap).
- Stored procedures and views (preview behind
experimental: pgcatalog).