TavernKeeper Scan Report

owler-tavern/context-image-generation

Commit 477549f Reviewed

No material or immediate-danger concern was identified in this review.

This advisory report describes what the named tools and review process found at one exact commit. Unknown or unobserved behavior may still exist.

0 immediate danger 0 material 3 low

What this review found

No material or immediate-danger item was identified.

Contextual expected matches (2)

JavaScript analysis reported javascript.download-to-execution

Expected behavior · high confidence

This is an image-generation extension, so contacting image APIs and downloading generated images is exactly what it should do. The API key you enter is sent only to the image provider you selected, which is normal and expected. No hidden code execution was found.

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 flags co-occurrence of network fetch primitives and a suspected code-execution sink. The visible fetch calls go to image-generation provider endpoints (linkapi.ai, tokenreply.com, local SillyTavern avatar/character routes) and download image bytes or JSON, which matches the extension's stated purpose. The API key is read from extension_settings and sent only as an Authorization header to the selected provider endpoint. No eval, Function constructor, import(), or command-execution primitive is present in the supplied source. The window.cigDebug assignment exposes pure helper functions for console debugging but does not execute remote code. arrayBufferToBase64 uses String.fromCharCode.apply and btoa for encoding, not code execution. The scanner correlation does not demonstrate a download-to-execution data flow.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule
javascript.download-to-execution
File role
production
Source
index.js:144-1074

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

The flagged file is a plain, readable list of provider settings and model definitions. There is no hidden or disguised code whatsoever. The scanner alert appears to be a false positive.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.obfuscated-code. The match applies to this repository.

Contextual assessment: Detailed technical wording was omitted by the public report safety filter.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule
javascript.xray.obfuscated-code
File role
production
Source
lib/providers/registry.js:1

Related contextual observations

Dev-only helper exposure on window object

low risk · high confidence

The extension exposes a few helper functions on the window object for developer debugging. This does not run remote code and only includes utility functions, not credential handling.

Technical assessment

The window.cigDebug assignment exposes isOpenAiImageModel, mapAspectRatioToSize, extractPromptText, parseImagesResponse, and requestLinkApiImage for console testing. These are pure or stateless helpers; no credential storage or dynamic evaluation is exposed. This is a common dev-aid pattern and does not constitute a code-execution sink.

Impact: none · Exploitability: unlikely

Developer action: none

Sources:

Coverage and limitations

JavaScript coverage

Tools

Limitations

Technical scan identity