informational*.sqlite*.db*.sqlite3

Local database files (.sqlite)

Local database files like .sqlite can hold real application data — sometimes copied from production — that an AI tool should not read.

This week: 1 repo in the scanned fleet exposed this category (3 matches).See Radar #4 →

What it is

SQLite and similar single-file databases store an application’s data on disk. During development they often accumulate real or production-like records.

Why it matters for AI context

If a database file is committed, an assistant can read its contents as binary or text context, exposing whatever records it contains. These files also bloat the repo and indexing.

How to keep it out of AI tools

  1. Keep working databases out of version control.
  2. Add *.sqlite, *.sqlite3, and *.db to .gitignore.
  3. Add the same patterns to your AI ignore file.
  4. Use migrations and seed scripts to recreate local data instead.
Add to your ignore file
*.sqlite
*.sqlite3
*.db

Ignore files that exclude this

FAQ

What if my app needs a checked-in database?
Commit only a small fixture with synthetic data, and exclude any database that may contain real or production records.

Check your own project

158 of 499 repos this week exposed sensitive paths to AI tools. Check yours in seconds:

Run the same local check with Offsend CLI:

brew install --cask offsend/tap/offsend-cli
offsend show
offsend prepare --dry-run

Everything runs locally. No file contents are uploaded.

Scan with Offsend CheckLearn more about Offsend →