TavernKeeper Advisory reports for Tavernary

TavernKeeper Scan Report

Zaakh/SillyTavern-zTracker

Commit 9759ea1 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 88 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

Some text-matching patterns in the bundled code could be slow with unusually crafted input, but no evidence shows a way for an attacker to actually cause this in normal use, and the worst case is a briefly stuck tab.

Technical evidence

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

Contextual assessment: The flagged regexes are part of bundled third-party parser libraries (Handlebars lexer token patterns, numeric and markup validators) in the generated bundle. The scanner did not retain the matched literals and no evidence shows attacker-controlled input reaching a pathologically backtracking expression under realistic chat-tracker usage. Worst plausible outcome is a slow or momentarily unresponsive tab on crafted input, which is a self-recoverable local denial of service.

Impact: low · Exploitability: unlikely

Developer action: Optionally audit the flagged expressions for linear-time behavior if untrusted tracker content is parsed with them; otherwise no action required.

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
generated
Source
dist/index.js:1

JavaScript analysis reported javascript.xray.unsafe-regex

Minor caution · medium confidence

Some pattern-matching code in the bundled libraries could run slowly if fed deliberately weird text. The worst outcome is the extension's own tab briefly lagging; there is no evidence of a way for an outside party to trigger this.

Technical evidence

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

Contextual assessment: The matched patterns are parsing regular expressions from bundled template, JSON, and XML libraries. Most are linear or anchored patterns over short strings, but a few with nested repetition and capture groups could exhibit backtracking slowdown on pathologically crafted input. In this client-side extension the inputs are locally generated tracker content and user-imported module files, so any resulting delay is a recoverable local slowdown of the user's own tab and does not constitute a concrete security harm. No attacker-controlled remote input path to these expressions is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Optionally audit the bundled parser dependency for known regex denial-of-service advisories and update it during routine maintenance; no urgent change is required.

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
generated
Source
dist/index.js:476
Deterministic technical evidence (71)

  • Dependency advisory GHSA-qx2v-qp2m-jg93:pkg:d0433ccd51b55fc561da06bf 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

  • Dependency advisory GHSA-gh4j-gqv2-49f6:pkg:2e769c3d435a393f7d6a63cc 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

  • Dependency advisory GHSA-8gc5-j5rx-235r:pkg:1ba011ced44a3aa03556255b 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

  • Dependency advisory GHSA-m7jm-9gc2-mpf2:pkg:eb295685e4f99fcf0f9aa306 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

  • Dependency advisory GHSA-h67p-54hq-rp68:pkg:032a72735b89e8109ae31a3d 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

  • Dependency advisory GHSA-9cx6-37pm-9jff:pkg:ca52f57e7f6518348696e910 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

  • Dependency advisory GHSA-fj3w-jwp8-x2g3:pkg:553721236f32a20b1e0db5b7 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

  • Dependency advisory GHSA-58qx-3vcg-4xpx:pkg:464f1e56f88977dff15c5c23 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

  • Dependency advisory GHSA-7p8r-x3mc-p8w7:pkg:2f8d75dd087c1050a99a8192 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

  • Dependency advisory GHSA-4c8g-83qw-93j6:pkg:181d5c1a6aff27dd93f86cff 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

  • Dependency advisory GHSA-3ppc-4f35-3m26:pkg:f700a97b2d134373c6c36877 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

  • Dependency advisory GHSA-3jxr-9vmj-r5cp:pkg:a6af0e9fdfc814bb2702c837 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

  • Dependency advisory GHSA-23c5-xmqv-rm74:pkg:28c6f8e6010383b649a97a01 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

  • Dependency advisory GHSA-3v7f-55p6-f55p:pkg:6567e5dee65459862e18aa65 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

  • JavaScript analysis reported javascript.xray.shady-link · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

    This technical signal is not part of the shipped runtime behavior.

    Policy reason: javascript-xray-inert-content · Execution scope: test-documentation-data

    Source: src/__tests__/extension-install.test.ts:10

  • Dependency advisory GHSA-v39h-62p7-jpjc:pkg:a6be302000b0d22d393bcd4e 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

  • Dependency advisory GHSA-442j-39wm-28r2:pkg:c54738cea96a333e19b8bd79 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

  • Dependency advisory GHSA-xhpv-hc6g-r9c6:pkg:4114756074b3c1883ca427a6 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

  • Dependency advisory GHSA-f65p-4m7j-42xc:pkg:92989e2d790a713a91b5bde1 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

  • JavaScript analysis reported javascript.xray.unsafe-regex · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

    This technical signal is not part of the shipped runtime behavior.

    Policy reason: javascript-unsafe-regex-inert · Execution scope: tooling-only

    Source: scripts/sync-version.mjs:16

  • Dependency advisory GHSA-mh99-v99m-4gvg:pkg:a3638530d49c16954a754a83 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

  • Dependency advisory GHSA-mh99-v99m-4gvg:pkg:f943bf04aa1d0078992a0950 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

  • Dependency advisory GHSA-3ppc-4f35-3m26:pkg:173c1b2fab8e025126fb982c 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

  • Dependency advisory GHSA-r28c-9q8g-f849:pkg:309438d8c981844c76003c01 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

  • Dependency advisory GHSA-xjpj-3mr7-gcpf:pkg:2c93c7ce30edf86304d17bbe 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

  • Dependency advisory GHSA-f886-m6hf-6m8v:pkg:16af9086b5e4ae9e3d4dc665 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

  • Dependency advisory GHSA-jp2q-39xq-3w4g:pkg:720a7f211d1f6e8a46d0f289 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

  • Dependency advisory GHSA-jmr7-xgp7-cmfj:pkg:0a170fd273ac9e64ed7e2bb5 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

  • Dependency advisory GHSA-xwg4-73v4-xw9w:pkg:b0abe8c9840bfaafb5747f78 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

  • Dependency advisory GHSA-7r86-cg39-jmmj:pkg:fa706fb036ae029fca4e7e55 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

  • Dependency advisory GHSA-rgw5-rvv9-x895:pkg:56fd66430fa2724b4206a4ad 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

  • Dependency advisory GHSA-xvcm-6775-5m9r:pkg:41b8ae801891d7b3fdae2f6e 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

  • Dependency advisory GHSA-v2hh-gcrm-f6hx:pkg:9600c6310040af533d8d1920 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

  • Dependency advisory GHSA-q3j6-qgpj-74h6:pkg:2d0d5c8fc1bb62c4e3b44b2a 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

  • Dependency advisory GHSA-7r86-cg39-jmmj:pkg:d1c7abe70f0b881829849922 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

  • Dependency advisory GHSA-2w6w-674q-4c4q:pkg:d25708df68737694eb8e6977 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

  • Dependency advisory GHSA-qj8w-gfj5-8c6v:pkg:7d87d343aa0c80bd7734851a 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

  • Dependency advisory GHSA-2qvq-rjwj-gvw9:pkg:bde04755dd174b8acbe6de92 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

  • Dependency advisory GHSA-6g55-p6wh-862q:pkg:be20184562ed7ac60b9bb3c5 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

  • Dependency advisory GHSA-2g4f-4pwh-qvx6:pkg:e75f751e62b1e8418f7d80f3 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

  • JavaScript analysis reported javascript.xray.shady-link · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

    This technical signal is not part of the shipped runtime behavior.

    Policy reason: javascript-xray-inert-content · Execution scope: test-documentation-data

    Source: src/__tests__/schema-to-example.test.ts:68

  • Dependency advisory GHSA-rgw5-rvv9-x895:pkg:19b149914c26cb2c9c5de439 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

  • Dependency advisory GHSA-jqff-g426-hqxp:pkg:f8eafe50099f6b486dd276b5 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

  • Dependency advisory GHSA-52cp-r559-cp3m:pkg:b50fc3b7dc4817b2367e97d7 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

  • Dependency advisory GHSA-mh29-5h37-fv8m:pkg:be84c0d3fc58da2798a815e5 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

  • Dependency advisory GHSA-2883-xcg3-v3hh:pkg:d14bd3188f5830360648dc9c 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

  • JavaScript analysis reported javascript.xray.serialize-environment · javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

    This technical signal is not part of the shipped runtime behavior.

    Policy reason: javascript-xray-inert-tooling · Execution scope: tooling-only

    Source: webpack.config.cjs:5

  • Dependency advisory GHSA-28wg-ghj8-5hjv:pkg:006e2a19c763cc0fc17b9679 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

  • Dependency advisory GHSA-fxqj-rqcc-2cmp:pkg:80dc2988b9d15a40674cea67 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

  • Dependency advisory GHSA-37qj-frw5-hhjh:pkg:e687e97ada633175cf3a9dbc 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

  • Dependency advisory GHSA-4x5r-pxfx-6jf8:pkg:4b1c458623d5edd1e246a805 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

  • Dependency advisory GHSA-c83g-rgw3-j3cx:pkg:9cc2e79628fa9edb09eb42da 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

  • Dependency advisory GHSA-2v37-7h3g-55p8:pkg:a9b17cadf83e3a5de547592b 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

  • Dependency advisory GHSA-8fgc-7cc6-rx7x:pkg:f80ec8e25f2f9f2ce4de54ab 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

  • Dependency advisory GHSA-7rx3-28cr-v5wh:pkg:2d05cf734c06fd6d1e77b848 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

  • Dependency advisory GHSA-p95v-992w-h6c3:pkg:5cae82464e421b021afa723a 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

  • Dependency advisory GHSA-fv7c-fp4j-7gwp:pkg:43dd868b8e2242ac0ba9d6d7 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

  • Dependency advisory GHSA-5c6j-r48x-rmvq:pkg:9695ebfe7ac51867550b15ed 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

  • Dependency advisory GHSA-c2c7-rcm5-vvqj:pkg:6159a1838ee53aace6ac3052 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

  • Dependency advisory GHSA-3jxr-9vmj-r5cp:pkg:0546a3b9043a41cf17d6475f 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

  • Dependency advisory GHSA-f886-m6hf-6m8v:pkg:3c9cac5b1efe1960955c0ea1 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

  • Dependency advisory GHSA-c2c7-rcm5-vvqj:pkg:09f761f2e2a83fdc7890eb5a 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

  • Dependency advisory GHSA-23c5-xmqv-rm74:pkg:129158f1f423f49b12e76a97 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

  • Dependency advisory GHSA-73wf-gq98-2v4g:pkg:f1a31653235e926160d3dd89 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

  • Dependency advisory GHSA-96hv-2xvq-fx4p:pkg:788f1d7067e1308f3b84ebcc 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

  • Dependency advisory GHSA-5p4m-2wfm-xmqj:pkg:854982e350d33df8baa91ad9 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

  • Dependency advisory GHSA-3v7f-55p6-f55p:pkg:972939a004a2a625fbda61c7 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

  • Dependency advisory GHSA-3mfm-83xf-c92r:pkg:146840b9eb3231ae1d463c20 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

  • Dependency advisory GHSA-38r7-794h-5758:pkg:3e2169c05cd6e65b3694dd1d 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

  • Dependency advisory GHSA-wf6x-7x77-mvgw:pkg:c54fb3802e9d37bdf9527043 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

  • Dependency advisory GHSA-v56q-mh7h-f735:pkg:85f01818ba1fa2d535c8fe80 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

Contextual expected matches (13)

JavaScript analysis reported javascript.download-to-execution

Expected behavior · high confidence

The code contacts only the local SillyTavern application to read lorebook data, which is what the extension says it does. Although the scanner saw both a network request and advanced code features in the same file, nothing shows the requested data being run as 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 decoded window shows the network primitives: same-origin requests to the local SillyTavern host for a CSRF token and for world-info retrieval by name, with the token sent only back to that same local endpoint as a header. This matches the project's documented World Info filtering feature. The response is handled through typed JSON parsing and defensive validation into structured objects; no fetched content is passed to an evaluation or command sink in the supplied code. The nearby dynamic-execution-style code is a transpiled generator runtime helper that constructs functions internally rather than evaluating remote strings, so the co-occurrence of a fetch primitive and a function sink does not establish a download-to-execution 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
generated
Source
dist/index.js:1

JavaScript analysis reported javascript.xray.monkey-patch

Expected behavior · high confidence

The scanner flagged code that modifies built-in JavaScript objects, but the actual code is a standard translation helper repeated many times inside the bundled build. It only sets up its own internal helper objects and does not replace anything in the host application.

Technical evidence

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

Contextual assessment: The flagged occurrences are repeated instances of a Babel-style regenerator runtime helper being inlined into the generated bundle: it defines constructor properties on its own newly created prototype objects and sets prototype links on objects it constructs. These are self-contained polyfill definitions on objects owned by the bundle, not reassignment or interception of host or third-party globals. The duplicated blocks across the file are repeated bundling of the same helper. No host function is replaced and no data flow to an attacker-controlled destination is shown.

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.monkey-patch
File role
generated
Source
dist/index.js:24531

JavaScript analysis reported javascript.xray.obfuscated-code

Expected behavior · high confidence

The code looks hard to read because it is the machine-minified build output, which is normal for distributed extensions. The readable original exists elsewhere in the project, and nothing in the supplied evidence suggests content deliberately hidden to evade review.

Technical evidence

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

Contextual assessment: The flagged file is the generated, minified distribution bundle for a browser extension. Minified variable names and dense single-line formatting are the expected output of a bundler and are disclosed by the project's build layout, where readable source lives outside dist. The scanner itself reports low confidence and supplies no matched literals. Reviewing the surrounding evidence windows shows recognizable library code (React, regenerator, JSON schema handling, a tracker UI) rather than concealment techniques such as string packing, hex decoding, or encrypted payloads. No hidden behavior is demonstrated.

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
generated
Source
dist/index.js:1

JavaScript analysis reported javascript.xray.prototype-pollution

Expected behavior · high confidence

The flagged code actually protects against the exact problem the scanner names: it blocks or renames a dangerous special key that attackers could use to tamper with core JavaScript objects. This is defensive coding from bundled libraries, not a flaw.

Technical evidence

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

Contextual assessment: The matched code is prototype-related but does not constitute pollution. One region builds a dictionary object with null prototype and marks dangerous keys as disabled, which is hardening. Other regions belong to a bundled XML parser that explicitly renames the special prototype key to a safe alternative before insertion, which is the standard defensive mitigation against prototype pollution. The remaining matches are the regenerator helper creating its own prototype chains. No recursive merge of untrusted keys into Object.prototype is present in the supplied evidence, so no attacker-controlled pollution path is demonstrated.

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.prototype-pollution
File role
generated
Source
dist/index.js:18559

JavaScript analysis reported javascript.xray.shady-link

Expected behavior · high confidence

The scanner saw web address-like text in the code, but these are standard official identifiers that libraries use internally, plus a safety check that blocks harmful script URLs. No suspicious destination is contacted.

Technical evidence

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

Contextual assessment: The matched literals are standard well-known namespace and schema identifiers used by bundled libraries: SVG and MathML namespace constants, XML namespace attributes, JSON Schema draft identifiers attached to the tracker's own schema objects, and React's built-in blocking of javascript URLs as a security precaution. None of these are outbound network destinations; they are compared string constants or schema metadata. No evidence shows data being transmitted to any suspicious or unexpected host.

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
generated
Source
dist/index.js:4033

JavaScript analysis reported javascript.download-to-execution

Expected behavior · medium confidence

The scanner noticed that the file both requests data and has some advanced code features somewhere inside it. But the actual requests go only to the local SillyTavern app itself, and nothing in the evidence shows downloaded content being executed as code.

Technical evidence

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

Contextual assessment: This is a whole-file correlation finding: the large generated bundle contains both a network primitive and a dynamic execution sink somewhere in the same file. The network usage shown in evidence is same-origin requests to the local SillyTavern host endpoints for a CSRF token and world-info retrieval, consistent with the project's documented purpose of filtering World Info for tracker generation. The dynamic-execution signals arise from bundled dependency code such as template and runtime helpers, not from a demonstrated pipeline that executes retrieved remote content. No evidence links a fetched response into an evaluation sink, so no download-to-execution flow is established.

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
generated
Source
dist/index.js:30-29294

JavaScript analysis reported javascript.xray.serialize-environment

Expected behavior · high confidence

The extension converts its own tracker data into text so it can be saved or edited, which is exactly what a stats-tracking extension should do. No sensitive information appears to be collected or sent out.

Technical evidence

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

Contextual assessment: The serialize-environment signal is a static heuristic typically triggered by serializing objects (for example JSON.stringify of tracker data for display, persistence, or export). The visible code shows tracker snapshots and module configurations being serialized into a settings textarea and stored structures, consistent with the extension's stated purpose of tracking and exporting chat stats. No evidence shows environment variables, credentials, or secret material being serialized or transmitted anywhere.

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.serialize-environment
File role
generated
Source
dist/index.js:57

JavaScript analysis reported javascript.xray.monkey-patch

Expected behavior · high confidence

The flagged code is a standard part of how build tools translate modern JavaScript for wider compatibility. It sets up internal plumbing for the extension's own code and does not tamper with the host application.

Technical evidence

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

Contextual assessment: The 54 monkey-patch signals correspond to repeated helper blocks that install properties on function prototypes and define constructor/prototype relationships. The supplied source shows these are the standard, verbatim-repeated regenerator-runtime helper pattern used by transpiled async generators, plus Handlebars prototype setup. This is normal bundled transpilation output, not runtime modification of host objects or SillyTavern internals.

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.monkey-patch
File role
generated
Source
dist/index.js:57

JavaScript analysis reported javascript.xray.serialize-environment

Expected behavior · high confidence

The scanner flagged data conversion code, but it only formats the extension's own tracker information for saving and display. Nothing sensitive like passwords or system details is involved.

Technical evidence

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.serialize-environment. 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.serialize-environment
File role
generated
Source
dist/index.js:23794

JavaScript analysis reported javascript.xray.shady-link

Expected behavior · high confidence

The flagged web addresses are just labels that standard web technologies require, such as SVG and schema identifiers. They are not calls to outside servers and nothing is sent to them.

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 links are well-known specification namespace strings embedded in bundled React DOM code (SVG, MathML, XML namespace URIs), the json-schema.org draft identifier used by tracker schema definitions, and React's own javascript-URL block message. These are inert string constants, not outbound network destinations, and no evidence shows data being sent to any external host.

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
generated
Source
dist/index.js:20

JavaScript analysis reported javascript.download-to-execution

Expected behavior · medium confidence

The file contains both code that can talk to the network and code that can build programs at runtime, because it bundles several common libraries. The evidence does not show any downloaded content actually being run as code, so this is not a demonstrated threat.

Technical evidence

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

Contextual assessment: This correlation rule fires when both a network-capable primitive and a dynamic-evaluation construct appear in the same bundle. The bundle contains fetch-capable runtime and template compilation code from bundled libraries (Handlebars compile, regenerator helpers), but the supplied evidence shows no data flow where content retrieved from the network is fed into an evaluation sink. The extension's own behavior centers on generating trackers via the host's model connections and displaying or persisting the results. Co-occurrence in a large minified bundle is not demonstrated exposure.

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
generated
Source
dist/index.js:1-57

JavaScript analysis reported javascript.xray.prototype-pollution

Expected behavior · high confidence

The flagged code actually contains safeguards that stop a known JavaScript trick where crafted input can corrupt core objects. It protects against the problem rather than causing it.

Technical evidence

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

Contextual assessment: The prototype-pollution signals correspond to bundled fast-xml-parser and Handlebars internals that explicitly check for the __proto__ key and rename it to a safe placeholder, plus prototype-based class wiring in transpiled helpers. This is defensive handling that mitigates prototype pollution during XML and template parsing, not an injection of properties into Object.prototype. No attacker-controlled path to polluting prototypes is demonstrated.

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.prototype-pollution
File role
generated
Source
dist/index.js:40

Credential access and network transmission in one file

Expected behavior · high confidence

The scanner saw a security token and a network request in the same file and raised a flag. Looking at the actual code, the token is a one-time security handshake that the extension fetches from the SillyTavern app itself and immediately hands back to that same app to authorize reading a lorebook. Nothing is sent to any outside service, and no passwords or API keys are involved. This is the normal, correct way for a SillyTavern extension to talk to its own host app.

Technical evidence

Scanner reason: A credential source and an outbound network operation were detected in the same file.

Contextual assessment: The scanner matched a credential source and an outbound network sink co-located in one file, but the actual data flow shows no exfiltration. The file retrieves a CSRF token via a relative-path fetch to the SillyTavern host's own endpoint, then uses that token solely in an X-CSRF-Token header on a same-origin POST to the host's world-info endpoint to load lorebook entries the user already has. Both requests use relative URLs, meaning they target the SillyTavern origin the extension runs in, not any external destination. The token is a per-session CSRF anti-forgery value, not a model-provider API key or user secret, and it is never logged, stored beyond a memoized promise, or transmitted anywhere except the host that issued it. The fetched lorebook content is mapped to a typed structure and returned to the caller, matching the extension's documented World Info filtering feature. This is standard client-side API usage for a SillyTavern extension and is proportionate to the stated project purpose.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
tavernkeeper 5
Rule
credential-exfiltration
File role
production
Source
src/sillytavern-world-info.ts:69

Related contextual observations

Scanner signals originate from bundled library code in the generated bundle

low risk · high confidence

The security scanner flagged patterns that come from common third-party building blocks the developer bundled into one file. Looking at the actual code, these are routine library internals, not suspicious behavior.

Technical assessment

The supplied source windows show the flagged patterns are verbatim-repeated regenerator-runtime helper blocks (prototype and GeneratorFunction wiring), fast-xml-parser __proto__ safeguards, Handlebars compiler and lexer internals, and React DOM namespace constants. These are standard outputs of bundling and transpiling well-known libraries into a single minified artifact, and none of the supplied evidence links them to host tampering, secret handling, or outbound data flow beyond the extension's stated purpose.

Impact: none · Exploitability: unlikely

Developer action: none

Sources:

Scanner signals originate from bundled dependencies in a generated build artifact

low risk · high confidence

Nearly all the scanner warnings trace back to standard third-party libraries that were packed into the extension's single build file. These libraries' normal internal code triggers the pattern-matching alerts; the extension's own logic shows no suspicious behavior in any of the supplied code samples.

Technical assessment

The supplied evidence windows consistently show code from well-known bundled libraries: a Babel-style regenerator runtime repeated as inline helpers, React DOM attribute and namespace handling, JSON Schema constants, a defensive XML parser, and Handlebars-style template parsing. The candidate flags (monkey-patch, obfuscated-code, prototype-pollution, shady-link, unsafe-regex, serialize-environment, download-to-execution) are all accounted for by these dependency patterns within one large minified bundle rather than by extension-authored logic. No candidate identifies extension code sending data to an external destination, concealing behavior beyond normal minification, or executing retrieved remote content.

Impact: none · Exploitability: unlikely

Developer action: none

Sources:

Coverage and limitations

Inventory
196 files · 13087033 bytes
Contextual coverage
86 of 86 candidates assessed

JavaScript coverage

Status
Incomplete
Candidates
124 files · 1931672 bytes
X-Ray review families
235 warning occurrences compacted to 15 evidence-preserving review families
Representations
124 raw · 25 decoded · 1 normalized · 0 bundle modules
Stage scans
124 raw signatures · 22 raw AST · 123 raw OpenGrep · 26 derived signatures · 1 derived AST · 23 derived OpenGrep

Unresolved JavaScript stages

Tools

Limitations

Technical scan identity
Full commit
9759ea1c46593ab5fbd51a633f26af880f592d57
Completed
History depth
20 commits
Method
Deterministic evidence with contextual review
Reviewer
nano-gpt.com · zai-org/glm-latest
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
4 fresh / 0 reused groups · 15 fresh / 0 reused candidates
Review source reports
none
Evidence triage
71 deterministic / 15 contextual candidates · 4 contextual / 17 total behavior cases
Model budget
3 model calls · 4 / 12 fresh cases · 94772 / 200000 estimated input · 87198 / 250000 actual input · 7043 / 40000 output tokens
Review batching
3 model calls · up to 2 groups and 8 candidates per call · 0 retry calls · 0 over-budget singleton calls
Review usage
87198 input · 7043 output · 1408 cache read · 1300 reasoning tokens
Report
f6a4e68c54990120b426982cd3a310fc9a70fb2b079171573c3c4233700553c8