Offline security workbench
NullID
A browser-first workspace for local security tasks, designed to keep data handling, trust decisions, recovery, and browser limits visible.
- Platform
- Browser/PWA + local Node CLI
- Scope
- Local files, text, notes, metadata, and packages
- Status
- 0.1.0 / current release
Problem
Security-adjacent file and text tasks are often scattered across unrelated tools. That fragmentation makes it harder to understand where data goes, what changed, and which limits apply.
NullID brings these tasks into one offline browser workspace without presenting the browser as a device-wide security console.
Trust Model
Local processing is the default. Files and text stay in the current browser session unless the user explicitly exports a result or saves local state.
The browser sandbox is a firm boundary: NullID does not claim visibility into operating-system processes, sockets, persistence, or firewall state.
Architecture
The application groups hashing, redaction, sanitization, metadata review, encryption, secure notes, and package inspection behind a shared local data model.
Workflows expose their inputs and outputs directly, while browser storage is used only where persistence is part of the chosen tool.
Interface
The interface uses a consistent workspace pattern: input, visible state, the current operation, and an explicit result. Trust summaries remain close to package and encryption workflows.
Navigation favors named tools and readable states over a dashboard that implies a single security score.
Failure Handling
Invalid files, unsupported formats, incomplete inputs, and unsuccessful operations return specific messages and a route back to the current task.
Destructive or irreversible actions require deliberate confirmation; browser limitations are explained where they affect the result.
Validation
Automated tests cover core transformations, localization, build output, keyboard flows, and browser behaviour. Playwright checks the primary workspaces and recovery paths across supported engines.
The same checks keep the offline build, metadata, and route structure consistent before a release is prepared.
Current State
The current 0.1.0 browser/PWA release is live, and the documented local Node CLI is part of the supported scope. The project remains an evolving current release rather than a finished product.
Both paths remain local-first and require no backend service or runtime external API. The Tauri bootstrap is experimental and is not a supported native desktop release.