TavernKeeper Scan Report

keepsanity/SillyTavern-Atelier

Commit 3b61946 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 2 low

What this review found

No material or immediate-danger item was identified.

Contextual expected matches (1)

JavaScript analysis reported javascript.xray.shady-link

Expected behavior · high confidence

This is just a default address for connecting to the user's own local image-generation software. It is exactly what the extension is supposed to do and poses no security concern.

Technical evidence

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

Contextual assessment: The flagged link is a default localhost URL (127.0.0.1:8188) for a local ComfyUI instance, matching the project's stated purpose of connecting to a user's local ComfyUI. It is a plain default configuration value with no exfiltration, obfuscation, or external destination.

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.shady-link
File role
production
Source
settings.js:7

Related contextual observations

Default local ComfyUI URL flagged as link signal

low risk · high confidence

The link the scanner noticed is just the default address for the user's own local image-generation program, which is what this extension is built to talk to.

Technical assessment

The scanner signal corresponds to the default comfyUrl value pointing to localhost:8188, the standard ComfyUI port. This is an inline default in the DEFAULTS object, consistent with the README requirement that ComfyUI be reachable from the SillyTavern host. No untrusted input flows to this value and no external destination is involved.

Impact: none · Exploitability: unlikely

Developer action: none

Sources:

Coverage and limitations

JavaScript coverage

Tools

Limitations

Technical scan identity