AI automation server with device management, task scheduling, and debug capabilities
Running the CLI starts a remote browser-control channel. Its peer can direct navigation, page interaction, and supplied JavaScript in browser contexts, including a connector intended to reuse an existing Chrome session.
At runtime it opens a long-lived WebSocket channel and executes received command messages.
dist/task/guada-browser-rpc-client.jsView on unpkg · L484A remotely selected browser_run_js method evaluates supplied code in an active browser page.
dist/task/guada-browser-rpc-client.jsView on unpkg · L278Package source references a known benign dynamic code generation pattern.
dist/task/guada-browser-rpc-client.jsView on unpkg · L282Source writes bytes from a remote response into a privileged operating-system path.
dist/executor/ios-wda-manager.jsView on unpkg · L1The main executable starts this remote browser RPC client after node authorization.
dist/index.jsView on unpkg · L103This report applies to @aiscene/aiserver@2.0.8.
See version security history for other recorded verdicts.
Evidence last updated: .
Package source references a known benign dynamic code generation pattern.
dist/task/guada-browser-rpc-client.jsView on unpkg · L282A remotely selected browser_run_js method evaluates supplied code in an active browser page.
dist/task/guada-browser-rpc-client.jsView on unpkg · L278At runtime it opens a long-lived WebSocket channel and executes received command messages.
Source writes bytes from a remote response into a privileged operating-system path.
dist/executor/ios-wda-manager.jsView on unpkg · L1The main executable starts this remote browser RPC client after node authorization.
dist/index.jsView on unpkg · L103