The flagged code simply sets up a helper that lets the extension's token counter download tokenizer files using the standard browser fetch function. There is no hidden code execution or dangerous behavior in these lines. This is normal functionality for an extension that counts tokens.
Technical evidence
Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution. The match applies to this repository.
Contextual assessment: Detailed technical wording was omitted by the public report safety filter.
postMessage uses wildcard origin for inter-frame capture data
low risk · high confidence
The extension uses a loose broadcasting method to send captured prompt data between parts of the page. Someone who could embed content in the page might send fake data that shows up in the viewer, but this only affects what is displayed and does not expose secrets or run code.
Technical assessment
The iframe fetch patch sends captured prompt data via window.postMessage with targetOrigin set to '*' (line 128), and the main-window message listener (line 161) does not verify the message origin. Any embedded iframe or other window with a reference to this window could post a message with _fpv:true and inject fabricated capture entries into the viewer history. The impact is limited to displaying incorrect data in the prompt viewer UI; no credentials are exposed and no code execution results. In the typical local single-origin SillyTavern deployment this is low risk, but specifying the expected origin on both send and receive sides would be a defense-in-depth improvement.
Impact: low · Exploitability: unlikely
Developer action: Restrict postMessage to the expected self-origin instead of '*' on the sending side, and verify event.origin in the message listener before processing _fpv messages.