oopsdb 1.3.0 → 1.5.0

package/README.md

@@ -4,6 +4,10 @@
 
 Auto-backup and 1-click restore for developers using Claude Code, Cursor, Windsurf, and other AI coding agents.
 
+<p align="center">
+  <img src="website/assets/oopsdb_demo.gif" alt="OopsDB Demo Screen Recording" style="max-width: 100%; border-radius: 8px; box-shadow: 0 4px 6px rgba(0,0,0,0.1)">
+</p>
+
 ---
 
 ## The Problem
@@ -78,6 +82,16 @@ oopsdb clean               Remove all OopsDB data from project
 2. `oopsdb watch` runs the native dump tool (`pg_dump`, `mysqldump`, or `sqlite3 .backup`) at your chosen interval. Output is streamed through AES-256-CBC encryption directly to disk — memory usage stays flat even for large databases.
 3. `oopsdb restore` shows your snapshots with timestamps and sizes. Pick one, confirm, and your database is rolled back. It takes a safety snapshot first, so you can always undo the undo.
 
+## Quick Demo
+
+Want to see OopsDB in action without touching your real database? We built a safe demo playground just for you.
+
+1. Clone or download this repository.
+2. Navigate to the `demo/` folder: `cd demo`
+3. Generate the dummy database: `sqlite3 test.db < seed.sql`
+4. Initialize OopsDB (it won't affect your global config because `.oopsdb` is gitignored here): `oopsdb init`
+5. Try running `oopsdb shield` and firing a `DROP TABLE users` against it to watch the interceptor catch the query!
+
 ## Requirements
 
 Your system needs the native database CLI tools:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oopsdb",
-  "version": "1.3.0",
+  "version": "1.5.0",
   "description": "Don't let AI nuke your database. Auto-backup and 1-click restore for developers using Claude Code, Cursor, Windsurf, and other AI coding agents.",
   "main": "dist/index.js",
   "bin": {