Safety mode: read-only + destructive-op confirmation (keyword heuristics)
- Dominant language
- Go
- Stars
- 218
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The headline feature. Keyword/prefix classification (no SQL parser — none covers all dialects; heuristics deliver the value): read-only mode allowlists SELECT/EXPLAIN/SHOW/WITH-SELECT; DDL/DML keywords require confirmation; per-source `readonly: true` in config. Parser-grade classification deliberately deferred.
**Acceptance:** in read-only mode no write statement reaches the driver (suite-tested per engine); confirm prompt on DROP/DELETE/UPDATE/ALTER/TRUNCATE/INSERT.
Contributor guide
Research direction
Start by locating the read-only mode, per-source configuration, driver execution path, and database-engine test suites. Trace how statements are classified and how confirmation prompts are handled. Done means read-only mode blocks writes for each engine and the listed destructive operations require confirmation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mysql, postgresql, sql, sqlite
- Domain
- cli, database, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100