opentui
Pass
Audited by Gen Agent Trust Hub on Feb 17, 2026
Risk Level: SAFEEXTERNAL_DOWNLOADSREMOTE_CODE_EXECUTIONCOMMAND_EXECUTIONPROMPT_INJECTION
Full Analysis
- Unverifiable Dependencies & Remote Code Execution (LOW): The documentation recommends initializing projects using
bunx create-tui@latestand installing libraries viabun install. These commands download and execute code from the npm registry under theanomalycoorganization, which is not verified as a trusted source. Although standard for the framework's use case, this pattern involves executing unvetted remote code. - Dynamic Execution (LOW): The skill documentation includes examples of using the
Bun.$API for shell command execution andBun.buildfor runtime compilation of native Zig code. These are powerful capabilities intended for TUI development that provide a vector for arbitrary command execution if not restricted. - Indirect Prompt Injection (LOW): The framework's input components and data-fetching patterns create a surface for indirect prompt injection if an agent processes untrusted data without sanitization.
- Ingestion points: File
references/components/inputs.md(input and textarea components) andreferences/react/patterns.md(API fetch examples). - Boundary markers: Absent; the documentation does not provide instructions for using delimiters or warnings to ignore embedded instructions in processed data.
- Capability inventory: File
references/core/gotchas.mdidentifies capabilities such asBun.$(shell) andBun.file(filesystem access). - Sanitization: Absent; no escaping or validation logic is demonstrated for handling external input.
Audit Metadata