dbinspect_bridge 0.1.0

Inspect the embedded databases inside your running Dart or Flutter application from a desktop client, over a paired, loopback-by-default connection.

Changelog

0.1.0

First release. The engine-neutral bridge core: the wire protocol, pairing, the transport and the release guard. It knows about no database.

• WebSocket transport with JSON-RPC framing, and a per-request deadline so one slow adapter cannot wedge a session.
• Pairing with a 40-bit code, compared in constant time, with per-session backoff and a limited number of attempts before pairing closes until the application restarts.
• Loopback is plain; anything else is TLS with a certificate generated for the session, its fingerprint printed in the pairing banner to be pinned.
• Methods: hello, listStores, getSchema, queryPage, rawQuery, insertRow, updateRow, deleteRow, snapshot, watch, unwatch. Every one beyond the first four is opt-in per adapter and refused by default.
• The release guard: bridgeEnabled is false in a release build, the bridge folds away and the protocol strings fold away with it. --dart-define=DBINSPECT_BRIDGE=true puts it back deliberately.

Adapters are separate packages, so using one never drags in the dependencies of the others: dbinspect_sqflite, dbinspect_drift, dbinspect_hive, and nitrite_bridge for Nitrite. dbinspect_mdns adds optional LAN discovery.