Browser Tools
Browser tools are convenience utilities for researchers, coordinators, and reviewers who need local processing without sending material to an external conversion, scanning, or inspection service. Each tool has a public contract that declares its route, component, processing model, network behavior, storage behavior, and practical limits.
These utilities are not evidence vaults, forensic suites, or exploit-development environments. They are narrow, transparent tools for common defensive and publication tasks: hashing files, transforming text-safe encodings, inspecting shallow file metadata, reviewing pasted headers, and decoding token structure.
Each tool must document what it reads, what it writes, whether any network request occurs, whether storage is used, and what input limits apply.
Tool Contract
Browser tools should be understandable without trusting hidden infrastructure. If a tool cannot meet the local-only contract, it should move to a separate reviewed category with explicit backend behavior.
Expansion Model
The browser-tool family now has a conversion model and a tool roadmap. Those pages explain which utilities can be added safely as local browser tools and which utilities require parser, dependency, or downloadable-release review. This keeps the tool surface useful without turning it into an unbounded collection of one-off widgets.