Expand description
Reusable core for Knife front ends and integrations.
The knife CLI, terminal interface, and external tools all consume these
modules instead of maintaining separate analysis paths.
Modules§
- address
- Explicit address kinds and checked conversions.
- analysis
- api
- Stable, presentation-neutral query types for Knife front ends.
- db
- The analysis database: what you worked out, kept between sessions.
- formats
- Format detection and dispatch. goblin does the heavy parsing; these modules
flatten its per-format structures into our neutral
Binarymodel. - listing
- The shared model behind a function listing.
- mcp
- A Model Context Protocol server (
knife mcp): a JSON-RPC 2.0 stream over stdio that exposes the analysis as tools, so an agent (ARGUS, or any MCP client) can drive knife directly. It reuses the same engine, listing, decompiler, and audit the command line does; only the wire format is new. - model
- The format-neutral model every analyzer fills in. Everything downstream (triage, disasm target selection, JSON export) talks to this, not to goblin.
- output
- Terminal rendering. One accent (violet), warm greys, colour tied to meaning.
- tools
- The read-tool catalog: one source of truth for every read-only analysis
query over a loaded
Session. - tui
- The interactive view: a function list, a listing, and cross-references, with your names and notes written straight through to the database.
- windows
- Deterministic Windows constants used by analysis and research front ends.
- workspace
- Shared analyzed-workspace loader used by every Knife front end.
Constants§
- ANALYSIS_
BUDGET - Default instruction-recovery budget used by interactive front ends.