Skip to content

Commit e4ab06c

Browse files
Add uv as a prerequisite (#740)
* Add uv as a prerequisite * Undo formatting changes --------- Co-authored-by: Greg Spencer <gspencergoog@users.noreply.github.com>
1 parent 9bb50c2 commit e4ab06c

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

samples/client/angular/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ These are sample implementations of A2UI in Angular.
55
## Prerequisites
66

77
1. [nodejs](https://nodejs.org/en)
8+
2. [uv](https://docs.astral.sh/uv/getting-started/installation/)
89

910
NOTE: [For the rizzcharts app](../../agent/adk/rizzcharts/), you will need GoogleMap API ([How to get the API key](https://developers.google.com/maps/documentation/javascript/get-api-key)) to display Google Map custome components. Please refer to [Rizzcharts README](./projects/rizzcharts/README.md)
1011

@@ -45,4 +46,4 @@ All operational data received from an external agent—including its AgentCard,
4546

4647
Similarly, any UI definition or data stream received must be treated as untrusted. Malicious agents could attempt to spoof legitimate interfaces to deceive users (phishing), inject malicious scripts via property values (XSS), or generate excessive layout complexity to degrade client performance (DoS). If your application supports optional embedded content (such as iframes or web views), additional care must be taken to prevent exposure to malicious external sites.
4748

48-
Developer Responsibility: Failure to properly validate data and strictly sandbox rendered content can introduce severe vulnerabilities. Developers are responsible for implementing appropriate security measures—such as input sanitization, Content Security Policies (CSP), strict isolation for optional embedded content, and secure credential handling—to protect their systems and users.
49+
Developer Responsibility: Failure to properly validate data and strictly sandbox rendered content can introduce severe vulnerabilities. Developers are responsible for implementing appropriate security measures—such as input sanitization, Content Security Policies (CSP), strict isolation for optional embedded content, and secure credential handling—to protect their systems and users.

0 commit comments

Comments
 (0)