A scanner flagged a possible suspicious link, but the code only connects to the extension's own local server and the Honcho memory service it needs to work. This is normal for this type of extension.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.shady-link in this repository.
Contextual assessment: The static analysis signal 'shady-link' at line 802 did not retain the matched literal value. The observed network calls in this file target a local server plugin path (PLUGIN_BASE) and the Honcho API service, both of which are within the extension's stated purpose of providing persistent memory via a proxy. The signal pattern alone, without a concrete external URL or destination, does not indicate malicious network behavior.
A scanner flagged the use of a system module that can access user information, but the plugin only uses it to read a settings file on your own computer. No data is being sent anywhere it shouldn't be.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.data-exfiltration in this repository.
Contextual assessment: Detailed technical wording was omitted by the public report safety filter.
The scanner thought there might be hidden or scrambled code, but looking at the actual file, all the code is normal and readable. It just imports standard SillyTavern modules.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code in this repository.
Contextual assessment: The scanner flagged obfuscated-code on line 1 of file, but the actual source shows standard ES module imports (from 'script.js', 'extensions.js', etc.) with no minification, encoding, or dynamic code generation. The entire file visible in the supplied source and expansions is plain, readable JavaScript. No obfuscated literal values were retained by the scanner, and the low scanner confidence indicates this is likely a false positive. The extension's code is well-structured and transparent.
The extension needs to both send requests over the network and run code to handle those requests, which is exactly what it is supposed to do. There is no sign of any hidden or dangerous code execution.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution in this repository.
Contextual assessment: The correlation of network retrieval (honchoFetch calls) and code execution sinks (async tool action functions) is inherent to this extension's design: it fetches context from the local Honcho proxy and uses registered function tools that execute memory operations. There is no use of eval, dynamic require, or any mechanism that would allow arbitrary code execution from untrusted input. The scanner's broad range (lines 152-1014) includes both patterns but not a demonstrated exploit path.