TavernKeeper Scan Report

brasen56/merged_world_tracker

Commit 3070611 Reviewed Aug 11, 2026

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 20 low

What this review found

No material or immediate-danger item was identified.

Minor cautions

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

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

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: world_state/provenance.js:47

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

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

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: chronicle/snapshots.js:56

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

A crafted input might briefly slow or freeze the local client, without showing broader security harm.

Technical evidence

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

Contextual assessment: The expression may permit a local CPU slowdown, but this evidence shows no credential, persistence, code-execution, or cross-user impact.

Impact: low · Exploitability: plausible

Developer action: Bound the input length or replace the expression when practical.

Scanner: javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1
Rule: javascript.xray.unsafe-regex
File role: production
Source: core/api.js:421

Deterministic technical evidence (4)

zizmor reported unpinned-uses · zizmor 1.28.0

The code has a known weakness, though this scan does not show that anyone can exploit it here.

Policy reason: zizmor-known-workflow-rule · Execution scope: automation

Source: .github/workflows/ci.yml:36
Dependency advisory GHSA-2v37-7h3g-55p8:pkg:c301f7c72c558e741e2a83a0 applies · osv-scanner 2.4.0

A dependency has a published security issue, though this scan does not show that the project exposes it to an attacker.

Policy reason: osv-structured-advisory · Execution scope: unknown

Source: package-lock.json
zizmor reported excessive-permissions · zizmor 1.28.0

The code has a known weakness, though this scan does not show that anyone can exploit it here.

Policy reason: zizmor-known-workflow-rule · Execution scope: automation

Source: .github/workflows/ci.yml:24-49
zizmor reported unpinned-uses · zizmor 1.28.0

The code has a known weakness, though this scan does not show that anyone can exploit it here.

Policy reason: zizmor-known-workflow-rule · Execution scope: automation

Source: .github/workflows/ci.yml:33

Contextual expected matches (13)

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

This file is not obfuscated or hidden—it's written clearly with comments explaining what each part does. The scanner warning is incorrect.

Technical evidence

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

Contextual assessment: The file is a well-structured, clearly commented JavaScript module. The 'obfuscated-code' signal at line 1 (a JSDoc comment) is a false positive with low scanner confidence. No obfuscation or concealment is present.

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: story_planner/generation.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

This file is written in plain, readable JavaScript with comments explaining what every function does. There is no hidden or scrambled code here.

Technical evidence

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

Contextual assessment: The JS-X-Ray obfuscated-code signal was triggered on file, but the supplied source code is fully readable, well-commented, uses standard ES module imports, and contains no obfuscation, minification, or encoded strings. The scanner confidence was low, and the signal is a false positive.

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: backup/render.js:1

zizmor reported artipacked

Expected behavior · medium confidence

This CI workflow only runs code quality checks. It does not save any files or handle passwords, so the alert is a false alarm.

Technical evidence

Scanner reason: zizmor matched workflow-security rule artipacked. The match applies to this repository.

Contextual assessment: The zizmor artipacked scanner rule flagged potential credential persistence through GitHub Actions artifacts, but the workflow (ci.yml) contains no `actions/upload-artifact` step, no credential or token references, and only runs lint and test. No artifact upload or credential exposure exists.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: artipacked
File role: tooling
Source: .github/workflows/ci.yml:32-33

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

This code helps the extension talk to SillyTavern's own systems. It's straightforward and safe.

Technical evidence

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

Contextual assessment: The file provides standard context helpers for accessing SillyTavern's internal state. No obfuscation is present. The scanner confidence was low; the signal is a false positive.

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: core/context.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

A security scanner flagged this file as possibly obfuscated, but reading the actual file shows ordinary, well-commented code that powers the extension's editing and settings screens. There is no hidden or scrambled code here, so this appears to be a false alarm.

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: world_state/render.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

This file contains normal, readable code with comments explaining its purpose. The scanner warning about obfuscation is not correct.

Technical evidence

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

Contextual assessment: This UI rendering file is clearly written with full JSDoc comments and straightforward logic. The 'obfuscated-code' signal at line 1 (a JSDoc comment) is a false positive with low scanner confidence. No actual obfuscation is present.

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: story_planner/render.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

This file is written in plain, readable JavaScript with comments explaining what every function does. There is no hidden or scrambled code here.

Technical evidence

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

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: chronicle/render.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

A security scanner thought this file might contain hidden code, but the actual code is open and clear. It does exactly what the extension's Knowledge feature needs to do.

Technical evidence

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

Contextual assessment: The scanner flagged obfuscated-code at line 1 of file, but the supplied source is standard, well-documented JavaScript with many imports and UI rendering logic. The code handles staging, notifications, and lorebook operations as expected for the Knowledge Tracker module. No obfuscation or hidden functionality is present.

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: knowledge/render.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

A security scanner flagged this file as potentially containing hidden code, but the actual code is written clearly and matches what the extension is supposed to do. It's a normal extension entry point.

Technical evidence

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

Contextual assessment: The scanner flagged obfuscated-code at line 1 of file, but the supplied source is plain, structured JavaScript with clear imports, comments, and a standard module entry point. The code handles dynamic imports from SillyTavern modules, which is expected for an extension. No obfuscation or concealed behavior is present.

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: index.js:1

JavaScript analysis reported javascript.download-to-execution

Expected behavior · high confidence

This extension needs to chat with an AI and use some built-in SillyTavern features. It does this safely—there's no way for an attacker to make it run dangerous code.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.download-to-execution. The match applies to this repository.

Contextual assessment: The file contains fetch() calls to an LLM API and a dynamic import() of a known SillyTavern module. No user-controlled dynamic code evaluation (eval, Function, setTimeout string) is present. The scanner likely flagged the combination of network fetch and import(), but import() uses a hardcoded relative path and is not a code execution sink.

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: core/api.js:55-143

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

A security scanner thought this file might have hidden code, but looking at the actual code shows it's written normally and does exactly what the extension description says. There's no secret trickery here.

Technical evidence

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

Contextual assessment: The scanner flagged obfuscated-code at line 1 of file, but the supplied source is standard, well-commented JavaScript with no obfuscation, minification, or string encoding. The file contains shared UI helpers and a floating button bar factory, consistent with its stated purpose. The scanner signal is a false positive from a generic static pattern.

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: core/ui.js:1

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

The code that handles chat commands and macros is clearly written and does exactly what you'd expect—no tricks or hidden code.

Technical evidence

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

Contextual assessment: The source code is clean, well-documented JavaScript registering SillyTavern slash commands and macros. There is no obfuscation present. The scanner confidence was low, and the signal is a false positive.

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: core/commands.js:1

JavaScript analysis reported javascript.xray.shady-link

Expected behavior · high confidence

The code uses a standard web address for SVG graphics, which is normal when drawing diagrams like a character relationship chart. It does not connect to the internet or send any data.

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 string is the standard SVG namespace URI used by the browser's SVG API. It appears in SVG rendering code that creates and manipulates SVG elements as part of the relationship graph visualisation feature, which is a documented capability of the extension. No external network connection, credential exposure, or data exfiltration is possible from this literal string; it is a static identifier required by all SVG application code.

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: knowledge/render.js:1767

Coverage and limitations

Inventory: 121 files · 2495132 bytes
Contextual coverage: 20 of 20 candidates assessed

JavaScript coverage

Status: Incomplete
Candidates: 99 files · 1777084 bytes
X-Ray review families: 16 warning occurrences compacted to 14 evidence-preserving review families
Representations: 99 raw · 24 decoded · 0 normalized · 0 bundle modules
Stage scans: 99 raw signatures · 99 raw AST · 99 raw OpenGrep · 24 derived signatures · 0 derived AST · 24 derived OpenGrep

Unresolved JavaScript stages

index.js — derived-ast / parse
index.js — normalize / parse
index.js — normalize / unsupported

Tools

inventory 0.1.0 — completed
tavernkeeper-static 5 — completed
gitleaks 8.30.1 — completed
opengrep 1.26.0 — completed
javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1 — completed
osv-scanner 2.4.0 — completed
zizmor 1.28.0 — completed
malcontent 1.25.7 — not-applicable

Limitations

This advisory review cannot prove the absence of unknown behavior.
JavaScript analysis was incomplete, so this first-filter scan supports no clean conclusion about unobserved behavior.

Technical scan identity

Full commit: 3070611a3a3364fdd784717c270a7cc367bd7f53
Completed: Aug 11, 2026
History depth: 20 commits
Method: Deterministic evidence with contextual review
Reviewer: nano-gpt.com · deepseek/deepseek-v4-flash:thinking
Scanner: 0.1.0
Scanner policy: 5
Rule catalog: 2
Contextual policy: 5
Ecosystem context: sillytavern-community-v1
Prompt: contextual-review-v7
Assessment schema: contextual-assessment-v2
Review provenance: 13 fresh / 0 reused groups · 13 fresh / 0 reused candidates
Review source reports: none
Evidence triage: 7 deterministic / 13 contextual candidates · 13 contextual / 17 total behavior cases
Model budget: 9 model calls · 13 / 12 fresh cases · 319145 / 200000 estimated input · 259049 / 250000 actual input · 11266 / 40000 output tokens
Review batching: 9 model calls · up to 3 groups and 3 candidates per call · 4 retry calls · 0 over-budget singleton calls
Review usage: 259049 input · 11266 output · 0 cache read · 0 reasoning tokens
Report: a3fac1337bdd8cf0833513f762372832bb98933c7b071c2ff7896b272668de4d