The extension fetches avatar images and sends image generation requests through SillyTavern's own backend. The timing function it uses takes a normal callback, not downloadable code. This is standard behavior for an image generation extension and poses no security risk.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution. The match applies to this repository.
Contextual assessment: The scanner correlated network retrieval (fetch) with a code execution sink in the same file. Examining the actual code, all fetch calls target either same-origin local avatar paths (/characters/..., user avatar URL) or SillyTavern's own backend endpoint /api/backends/chat-completions/generate. No external URLs are contacted. The only timing-related primitive is setTimeout with an inline arrow-function callback, which is not a dynamic code execution sink (no eval, no new Function, no string-based setTimeout). The request body includes reverse_proxy and proxy_password sourced from oai_settings, which is standard SillyTavern extension practice for proxying model requests through the backend. Data flow is confined to local SillyTavern APIs and the user-configured model provider via the backend. No concealed execution, exfiltration, or untrusted-input-driven code execution is present.
Proxy credentials forwarded to local SillyTavern backend API
low risk · high confidence
The extension sends proxy configuration from SillyTavern's settings to the backend API, which is normal for extensions that need proxy support.
Technical assessment
The requestBody includes reverse_proxy and proxy_password fields read from oai_settings and sent to SillyTavern's own /api/backends/chat-completions/generate endpoint. This is the standard pattern for SillyTavern extensions that support reverse proxy configuration. The credentials are not sent to any third-party or external destination; they go to the local backend which handles model-provider communication.