navig-blackbox
A standalone flight-recorder & crash black-box for any Python app: append-only event log, sys.excepthook crash capture, and sealed .navbox incident bundles. Installs without navig; also wired into
navig blackbox.
Works on its own — its own CLI, no navig required · v0.1.2 · PyPI
On its own (no navig needed)
pip install navig-blackbox
nbb --help # no navig needed
With navig
pip install "navig[blackbox]"
navig blackbox --help
Commands
| Command | What it does |
|---|---|
navig blackbox bundle create |
Create a .navbox bundle from recent events and logs. |
navig blackbox bundle export |
Re-export an existing .navbox bundle, optionally with encryption. |
navig blackbox bundle inspect |
Inspect the contents of a .navbox bundle. |
navig blackbox capture |
Capture a session snapshot to a .navbox bundle. |
navig blackbox clear |
Delete all recorded blackbox events (irreversible). |
navig blackbox crashes |
List recent crash reports. |
navig blackbox disable |
Pause event recording (events will not be written). |
navig blackbox enable |
Enable event recording. |
navig blackbox record |
Manually record an event into the blackbox. |
navig blackbox seal |
Seal the blackbox (prevents recording new events until unsealed). |
navig blackbox status |
Show blackbox recorder status and storage statistics. |
navig blackbox tail |
Show the most recent N events from the blackbox. |
navig blackbox timeline |
Render a Rich timeline table of recorded events. |
A free, standalone flight-recorder & crash black-box for any Python app — append-only event log,
sys.excepthookcrash capture, and sealed.navboxincident bundles — that installs without navig, and also backs thenavig blackboxcommand inside it.
The engine was lifted out of navig-core (navig/blackbox/) into this package so there is
one source of truth (the voice/→navig-audio pattern) — navig-core/navig/blackbox/* are
now thin re-export shims. Every navig-internal touchpoint (console, atomic writes, paths,
version, vault encryption) is routed through navig_blackbox._compat, which uses navig when
present and falls back cleanly when it isn't.
Install & use (standalone)
pip install navig-blackbox
nbb status # event count, on-disk size, sealed state, data dir
nbb record error "disk full" # append an event to the recorder
nbb events -n 100 # render the recent event timeline
nbb bundle -o incident.navbox # seal recent events + crashes + log tails into a .navbox
nbb inspect incident.navbox # read a bundle back (manifest + timeline)
nbb crashes # list captured crash reports
nbb seal / nbb unseal # freeze / resume recording for an investigation
# also: navig-blackbox --help · python -m navig_blackbox --help
Use as a library (any Python app)
from navig_blackbox import get_recorder, install_crash_handler, EventType
install_crash_handler() # unhandled exceptions → ~/.navig/blackbox/crashes/
get_recorder().record(EventType.COMMAND, {"command": "deploy", "args": "prod"})
from navig_blackbox import create_bundle, write_bundle
write_bundle(create_bundle(since_hours=4), "incident.navbox") # shareable postmortem archive
Inside navig
The command stays navig blackbox … (backed by this engine via the shim); ships as the optional
navig[blackbox] extra and registers a free Blackbox module tile. Encrypted .navbox export
(--encrypt) uses the navig vault key when navig is present, and falls back to a plaintext
archive (with a warning) standalone — data is never lost.
Apache-2.0.
Metadata
Release files for navig-blackbox 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| navig_blackbox-0.1.2.tar.gz | 32.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| navig_blackbox-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 61.1 kB
Security for navig-blackbox 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.