The scanner saw a network request and a code-execution-like pattern in the same file, but the network call goes to the local SillyTavern server to load lorebook data, and the result is used as text content, never executed as code.
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 a fetch call (line 631) with a code-execution sink in the same representation. The fetch targets the same-origin relative URL '/api/worldinfo/get' using context.getRequestHeaders() for auth headers, which is the standard SillyTavern backend API for loading world info/lorebook data. The response is parsed as JSON and used purely as data (entry content, keys, comments) to build prompt context — it is never passed to eval, Function, or any code execution primitive. The 'generateRaw' calls elsewhere in the file use SillyTavern's built-in LLM generation function, which sends prompts to the user's configured model API and returns text. Both the fetch and generateRaw are expected, proportionate behaviors for a scenario-generation extension whose README explicitly states it pulls in lorebook entries and generates scenarios via the LLM.
The scanner flagged this file as potentially obfuscated, but the code is plain, readable JavaScript building a UI modal with no hidden or disguised content.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code. The match applies to this repository.
Contextual assessment: The scanner flagged an obfuscated-code signal on line 1, but the supplied source is fully readable JavaScript: a class definition with clear imports, a constructor initializing state from settings, methods for loading templates, populating character/persona dropdowns, and constructing a jQuery-based modal dialog. No encoded strings, eval, hex escaping, or other obfuscation techniques are present. The code reads host state (characters, personas, chat context) and builds UI elements, which is expected behavior for a scenario-generation extension modal as described in the README. No credential access, external network calls, or concealed execution paths are present.
The extension fetches world info book data from the local SillyTavern server to display in a selection popup. This is exactly what the extension is supposed to do, and the data is safely escaped before being shown on screen. There is no dangerous code execution.
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 correlates a fetch call with a perceived code-execution sink. The fetch at line 210 targets '/api/worldinfo/get', the local same-origin SillyTavern server API, sending only a world-book name from the UI select element. The response JSON is parsed and rendered into jQuery template literals, but all user/world-info-controlled values (bookName, title, keys, content) are passed through escapeHtml() before insertion (lines 116, 120, 125-126, 156-160). There is no eval, Function constructor, innerHTML assignment with raw data, or other dynamic code execution sink. The loadWorldBook method first attempts to use SillyTavern's built-in context.loadWorldInfo, falling back to the local API. This is standard, expected behavior for a SillyTavern extension whose stated purpose includes selecting and displaying world info entries. No credentials are transmitted, no external destinations are contacted, and no obfuscation or persistence is present.
The scanner flagged this file as potentially obfuscated, but the code is plain, readable JavaScript with no hidden or disguised content.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code. The match applies to this repository.
Contextual assessment: The scanner flagged an obfuscated-code signal on line 1, but the supplied source is fully readable, well-structured JavaScript with clear imports, named functions, comments, and standard SillyTavern extension patterns (jQuery initialization, slash command registration, dynamic imports for settings/modal/generator modules). No encoded strings, eval, hex escaping, string array rotation, or other obfuscation techniques are present. The code performs standard extension initialization: loading a stylesheet, importing dependencies, creating a modal instance, registering slash commands, and adding a UI button to the extensions menu. No concealed execution, credential access, or external network calls are present.
The scanner flagged this file as potentially obfuscated, but the code is plain, readable JavaScript for managing extension settings with no hidden or disguised content.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code. The match applies to this repository.
Contextual assessment: The scanner flagged an obfuscated-code signal on line 1, but the supplied source is fully readable JavaScript with clear imports, a settings constants object, localStorage persistence, jQuery HTML template construction for settings UI, and event listener setup. No encoded strings, eval, hex escaping, or other obfuscation techniques are present. The module stores user-configurable settings (writing style prompt, tone, connection profile, context options, injection depth) in localStorage and syncs via SillyTavern's saveSettingsDebounced. This is standard and proportionate behavior for an extension settings module as described in the README. No credential exfiltration, external network calls, or concealed execution paths are present.