The scanner noticed both a network request and command execution in the same file. In reality, the request fetches a local chat list and the commands are hardcoded actions like delete-chat. No data from the network request flows into the commands, so there is no dangerous download-to-execution path.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution. The match applies to this repository.
Contextual assessment: The network retrieval is fetch('/api/characters/chats') posting a character avatar to the local SillyTavern server; the JSON response is only mapped to chat file names for a dropdown. The execution sinks identified are executeSlashCommandsWithOptions('/delchat') and SlashCommandParser.commands['api'/'model'].callback, all invoked with hardcoded string literals for the extension's stated delete-chat and status-display features. There is no data flow from the fetch response into any execution sink. SVGInject operates on a local /img/{modelName}.svg path derived from getGeneratingApi(), not from network-controlled input. The correlation is coincidental coexistence in one file, not a download-to-execution chain.
The scanner thought it saw hidden or obfuscated code, but the actual source is clearly written, readable JavaScript for a SillyTavern chat toolbar extension. There is nothing concealed.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code. The match applies to this repository.
Contextual assessment: The flagged line 1 is a standard destructuring assignment from SillyTavern.getContext() followed by ES module imports. The full source is readable, uses clear naming, plain comments, and standard DOM manipulation patterns. No eval, encoded strings, packed code, string-table obfuscation, or concealed logic is present. The scanner signal is a low-confidence false positive on the module/destructuring syntax pattern.