AgentReadyHomeAgent Listing

← assistant-ui

assistant-ui — agentic threat model

6.2AIVSS 6.2 · Medium

assistant-ui is a frontend React library rather than an autonomous agent, meaning its direct agentic risk is negligible; however, client-side security risks like XSS or data exposure exist if it is integrated insecurely with backend LLM orchestrators.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 6.1AARS uplift 0.12Factor sum 0.3/10Threat ×1.0Mitigation ×1.0
Autonomy of Action
0.00
Goal-Driven Planning
0.00
Self-Modification
0.00
Dynamic Tool Use
0.00
Persistent Memory
0.00
Contextual Awareness
0.10
Dynamic Identity
0.00
Multi-Agent Interactions
0.00
Non-Determinism
0.10
Opacity & Reflexivity
0.10

Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.

MAESTRO 7-layer threat model

Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.

L1 · Foundation Models⚠ not certain from listing

Not certain from the listing — assistant-ui is a frontend library and does not bundle or run foundation models directly, though it connects to them via SDKs.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — The library handles UI rendering of chat messages and does not manage vector databases or RAG data operations directly.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — While it integrates with Langchain and Vercel AI SDK, the library itself is a UI layer and does not orchestrate agent planning or tool execution.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — As a React library, deployment depends entirely on the host application's frontend infrastructure and has no built-in hosting or sandboxing.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — The library focuses on UI rendering and does not provide LLM evaluation, guardrails, or observability logging out of the box.

L6 · Security & Compliance (cross-cutting)⚠ not certain from listing

Not certain from the listing — Security controls like authentication, authorization, and input sanitization (beyond basic markdown rendering) must be implemented by the parent application.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — The library does not participate in multi-agent marketplaces or ecosystem-level orchestrations directly, acting only as the presentation layer.

MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).