TavernKeeper Scan Report

AventurasTeam/Aventuras

Commit 267d15f Reviewed Aug 13, 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 86 low

What this review found

No material or immediate-danger item was identified.

Minor cautions

Gitleaks reported generic-api-key

Minor caution · high confidence

This extension stores a search token directly in the code so it can look up characters from JannyAI. Anyone can find this token, but it only allows searching public character lists—nothing private or dangerous.

Technical evidence

Scanner reason: Gitleaks matched secret-detection rule generic-api-key. The match applies to this repository.

Contextual assessment: The constant FALLBACK_TOKEN on line 9 is a hardcoded API token used as a fallback for authenticating search requests to the JannyAI public search API. The token is embedded in client-side source code, making it trivially extractable by anyone who inspects the application. However, the token grants read-only access to a public character/scenario search index—equivalent to what a browser visiting the JannyAI website already has. The code first attempts to fetch a fresh token dynamically from JannyAI's client-side config and only falls back to this hardcoded value. There is no evidence of user credential exposure, exfiltration, or other sensitive data access. The concrete harm is limited to an attacker being able to perform the same public searches the app performs, which is proportionate to the stated project purpose of discovering characters from JannyAI.

Impact: low · Exploitability: readily_exploitable

Developer action: Consider removing the hardcoded fallback token and relying entirely on the dynamic fetch, or documenting that this token is a public, non-sensitive value used only for read-only search access. If the token is intentionally public, suppress the scanner alert with an inline comment.

Scanner: gitleaks 8.30.1
Rule: generic-api-key
File role: production
Source: src/lib/services/discovery/providers/janny.ts:9

Deterministic technical evidence (78)

Dependency advisory RUSTSEC-2025-0080:pkg:d9db6230dfa23e8ba0fa93cf 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: src-tauri/Cargo.lock
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/release.yml:108
zizmor reported cache-poisoning · 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:95
Dependency advisory RUSTSEC-2024-0414:pkg:e12ed7daa8c1d8360f101be8 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: src-tauri/Cargo.lock
zizmor reported cache-poisoning · 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:42
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:113
Dependency advisory GHSA-72xf-g2v4-qvf3:pkg:2f098d09dffd8939e104e6f0 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-2mjp-6q6p-2qxm:pkg:6d96a46fadb25a056091e448 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-m8rv-5g2x-5cg5:pkg:4960f6321d5eb83e948ad4ac 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 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:67
Dependency advisory GHSA-g8m3-5g58-fq7m:pkg:e4124745cfdd4bc7b9a15ac1 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 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:92
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/release.yml:102
Dependency advisory GHSA-v3r7-h72x-cjcm:pkg:3442b6d04e2f119213e16797 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-5v7r-6r5c-r473:pkg:db1c36cdfd066cb137608ca0 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-vrm6-8vpv-qv8q:pkg:0b992fe91b0b56ff0c3a69a0 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 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/release.yml:43
Dependency advisory GHSA-vxpw-j846-p89q:pkg:2b5722d889310f1a977423f1 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 RUSTSEC-2024-0411:pkg:7048d8a9d3d0f0ec2dd07bfe 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: src-tauri/Cargo.lock
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:42
Dependency advisory RUSTSEC-2023-0071:pkg:ee975215c8fb081d4be2c2de 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: src-tauri/Cargo.lock
Dependency advisory GHSA-pxg6-pf52-xh8x:pkg:6da1e3539f31ff57c2a349c3 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 cache-poisoning · 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/release.yml:46
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/release.yml:97
Dependency advisory RUSTSEC-2024-0370:pkg:9b268f40461da81c7a1c55ed 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: src-tauri/Cargo.lock
Dependency advisory GHSA-w5hq-g745-h8pq:pkg:557a6d9a353e8755eba18deb 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 RUSTSEC-2024-0413:pkg:c2f358c9f3bc98a14e0c2abf 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: src-tauri/Cargo.lock
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/release.yml:66
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: scripts/remote.test.js:10
Dependency advisory GHSA-wrw7-89jp-8q8g:pkg:4b30aae73f1836d87a5b008c 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: src-tauri/Cargo.lock
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/release.yml:87
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:39
zizmor reported cache-poisoning · 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/release.yml:90
Dependency advisory RUSTSEC-2025-0081:pkg:5c764120c78ffcfe5027b39c 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: src-tauri/Cargo.lock
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/release.yml:146
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/release.yml:18
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:116
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:48
Dependency advisory GHSA-fjxv-7rqg-78g4:pkg:6c89c9914b40635e432f1415 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-hmw2-7cc7-3qxx:pkg:b55f5aef11b0369cc46f988a 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-6rw7-vpxm-498p:pkg:43bb4aeefd1a794ecdaf18ba 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 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/release.yml:152
zizmor reported cache-poisoning · 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:53
Dependency advisory RUSTSEC-2024-0429:pkg:d2e88fc02f6be9987f66e6e8 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: src-tauri/Cargo.lock
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/lint-and-typecheck.yml:19
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/release.yml:90
Dependency advisory GHSA-35p6-xmwp-9g52:pkg:d8c1871761b9627fdd34c81b 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: vite.config.js:5
Dependency advisory GHSA-8xcm-r25x-g524:pkg:cc5804616c4fb4e83e60068a 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 RUSTSEC-2026-0235:pkg:d039eb756756d5d8fe092ddd 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: src-tauri/Cargo.lock
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:151
Dependency advisory RUSTSEC-2025-0100:pkg:bd8adf60c37242745cb633a0 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2024-0418:pkg:b245323ca01b322dae07bf9b 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2024-0420:pkg:d1377594ef97b5997d1bd6e4 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2024-0415:pkg:7feb02dbce543e0572f8f169 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2025-0075:pkg:3e15a087e2f1d00bbc8d944a 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2025-0098:pkg:bc6e2fc910a7ca702c31e56a 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: src-tauri/Cargo.lock
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/lint-and-typecheck.yml:16
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/release.yml:46
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/version.js:14
Dependency advisory RUSTSEC-2024-0416:pkg:c8c328b18837aef0f997eeec 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: src-tauri/Cargo.lock
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:95
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:13
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/lint-and-typecheck.yml:12-35
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/release.yml:52
Dependency advisory GHSA-p8p7-x288-28g6:pkg:e8e7ad0090121b0f387eaa27 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-p88m-4jfj-68fv:pkg:0aa6e836b145749eb5c5bae2 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-4992-7rv2-5pvq:pkg:787189633d8ba93446193680 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 RUSTSEC-2024-0419:pkg:694df782baf029578982f056 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: src-tauri/Cargo.lock
Dependency advisory RUSTSEC-2024-0412:pkg:4216c3e2f95d873b67813c23 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: src-tauri/Cargo.lock
Dependency advisory GHSA-v9p9-hfj2-hcw8:pkg:272b59ddefffdd1746f88817 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 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:53
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:107
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:157
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/release.yml:111
Dependency advisory GHSA-g9mf-h72j-4rw9:pkg:2ae61459d96677abe6b160ba 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 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:102
Dependency advisory RUSTSEC-2024-0417:pkg:38b1a8e2b331be3a60dc921d 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: src-tauri/Cargo.lock

Contextual expected matches (7)

zizmor reported artipacked

Expected behavior · high confidence

A security scanner flagged a regular checkout step as possibly leaking secrets into build artifacts. However, the workflow does not create any artifacts in this job, so there's no risk. This is a common false positive.

Technical evidence

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

Contextual assessment: The zizmor artipacked rule flagged a standard `actions/checkout@v4` step in the build-desktop job of the Pre-release workflow. The rule detects potential credential persistence through GitHub Actions artifacts, but no artifact upload step exists in this job. Secrets (GITHUB_TOKEN, TAURI_SIGNING_PRIVATE_KEY, TAURI_SIGNING_PRIVATE_KEY_PASSWORD) are consumed by the tauri-action and not written to any file that could be uploaded. The scanner confidence is low, and the evidence shows no actual data flow from secrets to artifacts.

Impact: none · Exploitability: unlikely

Developer action: none

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

zizmor reported superfluous-actions

Expected behavior · high confidence

A scanner suggested that a third-party action used to upload release files could be replaced with GitHub's built-in tools. It's a style suggestion, not a security problem.

Technical evidence

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

Contextual assessment: The zizmor superfluous-actions rule flagged the use of `softprops/action-gh-release@v1` for uploading the Android APK to a release. The rule notes that GitHub's built-in `actions/upload-release-asset` or a simpler step could be used instead. This is a code-style recommendation, not a security vulnerability. The action is a widely used third-party action, and there is no evidence of malicious behavior or security weakness in its usage here.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: superfluous-actions
File role: tooling
Source: .github/workflows/ci.yml:157

zizmor reported artipacked

Expected behavior · high confidence

A scanner flagged a routine code checkout step. Even though this job uploads a built app file, the checkout doesn't cause any secret to leak. No action needed.

Technical evidence

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

Contextual assessment: The zizmor artipacked rule flagged a standard `actions/checkout@v4` step in the build-android job of the Pre-release workflow. While this job does upload an artifact (the signed APK), the checkout step itself does not introduce credentials into the artifact. Secrets are only used in later steps for keystore decoding and signing, and the final APK does not include those secrets. The scanner confidence is low, and there is no demonstrated path for credentials to persist in artifacts.

Impact: none · Exploitability: unlikely

Developer action: none

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

zizmor reported artipacked

Expected behavior · high confidence

A scanner flagged a routine checkout step in a release build. Even though the build uses secret keys to sign the app, those secrets don't end up in the uploaded file because of this checkout. No risk.

Technical evidence

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

Contextual assessment: The zizmor artipacked rule flagged a standard `actions/checkout@v4` step in the build-android job of the Release workflow. Although this job handles Android signing secrets (ANDROID_KEYSTORE_BASE64, ANDROID_KEYSTORE_PASSWORD, etc.) and uploads the signed APK as an artifact, the checkout step itself does not expose those secrets. Secrets are injected later via environment variables and used only in the signing commands; they are not written into the repository checkout that becomes part of the artifact. The scanner confidence is low, and there is no demonstrated credential persistence.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: artipacked
File role: tooling
Source: .github/workflows/release.yml:86-87

zizmor reported artipacked

Expected behavior · high confidence

A scanner flagged a checkout step in a workflow that only runs code checks. No secrets or uploads exist, so there is no risk. This is a false positive.

Technical evidence

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

Contextual assessment: The zizmor artipacked rule flagged a standard `actions/checkout@v4` step in the lint-and-typecheck workflow. This workflow does not use any secrets or upload any artifacts; it only runs build, lint, and type-check commands. There is no mechanism for credential persistence. The scanner confidence is low, and the finding is a false positive.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: artipacked
File role: tooling
Source: .github/workflows/lint-and-typecheck.yml:15-16

zizmor reported artipacked

Expected behavior · high confidence

A scanner flagged a routine checkout step in a desktop release build. The build signs and uploads files, but the checkout doesn't cause any secret leakage. No action needed.

Technical evidence

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

Contextual assessment: The zizmor artipacked rule flagged a standard `actions/checkout@v4` step in the build-desktop job of the Release workflow. The desktop job uses the tauri-action with signing secrets (GITHUB_TOKEN, TAURI_SIGNING_PRIVATE_KEY, etc.) and releases desktop binaries. The artifact uploads are handled by the tauri-action, and the checkout step does not cause secrets to persist in artifacts. The scanner confidence is low, and there is no demonstrated data flow from checkout to credential exposure.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: artipacked
File role: tooling
Source: .github/workflows/release.yml:42-43

zizmor reported superfluous-actions

Expected behavior · high confidence

The scanner noted that a third-party action used to upload files to a GitHub release could be replaced by a built-in GitHub feature. This is a suggestion for optimization, not a security problem. The action itself is safe and commonly used.

Technical evidence

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

Contextual assessment: The zizmor scanner rule 'superfluous-actions' flagged the use of softprops/action-gh-release@v1 because its functionality (creating or updating a GitHub Release and uploading assets) can be replaced by the built-in GitHub CLI or REST API. This is a workflow-optimization advisory, not a security vulnerability. The action is a legitimate, widely-used third-party action and does not introduce any attacker-controlled data flow, credential exposure, or unauthorized behavior. The workflow uses the action with a GITHUB_TOKEN scoped to the repository, which is expected for release automation. No security concern exists.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: zizmor 1.28.0
Rule: superfluous-actions
File role: tooling
Source: .github/workflows/release.yml:152

Coverage and limitations

Inventory: 830 files · 9847061 bytes
Contextual coverage: 86 of 86 candidates assessed

JavaScript coverage

Status: Incomplete
Candidates: 398 files · 2915273 bytes
X-Ray review families: 3 warning occurrences compacted to 3 evidence-preserving review families
Representations: 398 raw · 20 decoded · 0 normalized · 0 bundle modules
Stage scans: 398 raw signatures · 66 raw AST · 398 raw OpenGrep · 20 derived signatures · 0 derived AST · 20 derived OpenGrep

Unresolved JavaScript stages

scripts/release.js — derived-ast / parse
scripts/release.js — normalize / parse
src/lib/components/settings/advancedPanelView.test.ts — raw-ast / parse
src/lib/components/settings/advancedPanelView.ts — raw-ast / parse
src/lib/components/ui/alert/index.ts — raw-ast / parse
src/lib/components/ui/badge/index.ts — raw-ast / parse
src/lib/components/ui/button/index.ts — raw-ast / parse
src/lib/components/ui/drawer/index.ts — raw-ast / parse
src/lib/components/ui/responsive-modal/context.ts — raw-ast / parse
src/lib/components/ui/toggle/index.ts — raw-ast / parse
src/lib/components/vault/prompts/sampleContext.ts — raw-ast / parse
src/lib/components/vault/prompts/templateGroups.ts — raw-ast / parse
src/lib/components/wizard/wizardTypes.ts — raw-ast / parse
src/lib/constants/modelHealth.ts — raw-ast / parse
src/lib/log.ts — raw-ast / parse
src/lib/services/ai/BaseAIService.ts — raw-ast / parse
src/lib/services/ai/core/config.ts — raw-ast / parse
src/lib/services/ai/core/defaults.ts — raw-ast / parse
src/lib/services/ai/core/factory.ts — raw-ast / parse
src/lib/services/ai/core/reasoning.test.ts — raw-ast / parse
src/lib/services/ai/core/reasoning.ts — raw-ast / parse
src/lib/services/ai/core/types.ts — raw-ast / parse
src/lib/services/ai/generation/ActionChoicesService.ts — raw-ast / parse
src/lib/services/ai/generation/ClassifierService.ts — raw-ast / parse
src/lib/services/ai/generation/MemoryService.ts — raw-ast / parse
src/lib/services/ai/generation/NarrativeService.test.ts — raw-ast / parse
src/lib/services/ai/generation/NarrativeService.ts — raw-ast / parse
src/lib/services/ai/generation/StyleReviewerService.ts — raw-ast / parse
src/lib/services/ai/generation/SuggestionsService.ts — raw-ast / parse
src/lib/services/ai/generation/WorldStateInjector.test.ts — raw-ast / parse
src/lib/services/ai/generation/WorldStateInjector.ts — raw-ast / parse
src/lib/services/ai/generation/index.ts — raw-ast / parse
src/lib/services/ai/image/BackgroundImageService.ts — raw-ast / parse
src/lib/services/ai/image/ImageAnalysisService.ts — raw-ast / parse
src/lib/services/ai/image/InlineImageService.ts — raw-ast / parse
src/lib/services/ai/image/InlineImageTracker.ts — raw-ast / parse
src/lib/services/ai/image/imageUtils.ts — raw-ast / parse
src/lib/services/ai/image/index.ts — raw-ast / parse
src/lib/services/ai/image/providers/a1111.ts — raw-ast / parse
src/lib/services/ai/image/providers/chutes.ts — raw-ast / parse
src/lib/services/ai/image/providers/comfy.ts — raw-ast / parse
src/lib/services/ai/image/providers/fetchAdapter.ts — raw-ast / parse
src/lib/services/ai/image/providers/google.ts — raw-ast / parse
src/lib/services/ai/image/providers/nanogpt.ts — raw-ast / parse
src/lib/services/ai/image/providers/openai.ts — raw-ast / parse
src/lib/services/ai/image/providers/openrouter.ts — raw-ast / parse
src/lib/services/ai/image/providers/pollinations.ts — raw-ast / parse
src/lib/services/ai/image/providers/registry.test.ts — raw-ast / parse
src/lib/services/ai/image/providers/registry.ts — raw-ast / parse
src/lib/services/ai/image/providers/types.ts — raw-ast / parse
src/lib/services/ai/image/providers/zhipu.ts — raw-ast / parse
src/lib/services/ai/index.ts — raw-ast / parse
src/lib/services/ai/lorebook/LoreManagementService.ts — raw-ast / parse
src/lib/services/ai/lorebook/entryFields.ts — raw-ast / parse
src/lib/services/ai/lorebook/entryState.ts — raw-ast / parse
src/lib/services/ai/lorebook/index.ts — raw-ast / parse
src/lib/services/ai/lorebook/sessionChanges.test.ts — raw-ast / parse
src/lib/services/ai/lorebook/sessionChanges.ts — raw-ast / parse
src/lib/services/ai/retrieval/AgenticRetrievalService.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/AgenticRetrievalService.ts — raw-ast / parse
src/lib/services/ai/retrieval/EntryRetrievalService.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/EntryRetrievalService.ts — raw-ast / parse
src/lib/services/ai/retrieval/TimelineFillService.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/TimelineFillService.ts — raw-ast / parse
src/lib/services/ai/retrieval/alreadyInContext.ts — raw-ast / parse
src/lib/services/ai/retrieval/chapterContentBudget.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/chapterContentBudget.ts — raw-ast / parse
src/lib/services/ai/retrieval/grepSampling.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/grepSampling.ts — raw-ast / parse
src/lib/services/ai/retrieval/index.ts — raw-ast / parse
src/lib/services/ai/retrieval/recentTail.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/recentTail.ts — raw-ast / parse
src/lib/services/ai/retrieval/retrievalHistory.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/retrievalHistory.ts — raw-ast / parse
src/lib/services/ai/retrieval/retrievalSnapshot.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/retrievalSnapshot.ts — raw-ast / parse
src/lib/services/ai/retrieval/stickiness.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/stickiness.ts — raw-ast / parse
src/lib/services/ai/retrieval/tier2SecondPass.ts — raw-ast / parse
src/lib/services/ai/retrieval/tier3Selection.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/tier3Selection.ts — raw-ast / parse
src/lib/services/ai/retrieval/timelineFillGrouping.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/timelineFillGrouping.ts — raw-ast / parse
src/lib/services/ai/sdk/agents/factory.ts — raw-ast / parse
src/lib/services/ai/sdk/agents/index.ts — raw-ast / parse
src/lib/services/ai/sdk/agents/stopConditions.test.ts — raw-ast / parse
src/lib/services/ai/sdk/agents/stopConditions.ts — raw-ast / parse
src/lib/services/ai/sdk/generate.ts — raw-ast / parse
src/lib/services/ai/sdk/index.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/index.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/logging.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/patchResponse.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/promptSchema.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/retryMiddleware.ts — raw-ast / parse
src/lib/services/ai/sdk/middleware/uniqueToolCallId.ts — raw-ast / parse
src/lib/services/ai/sdk/presetResolution.test.ts — raw-ast / parse
src/lib/services/ai/sdk/presetResolution.ts — raw-ast / parse
src/lib/services/ai/sdk/providers/config.ts — raw-ast / parse
src/lib/services/ai/sdk/providers/fetch.ts — raw-ast / parse
src/lib/services/ai/sdk/providers/index.ts — raw-ast / parse

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 — completed

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: 267d15f2b487292e855704d6188c5a81766e1680
Completed: Aug 13, 2026
History depth: 6 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: 7 fresh / 0 reused groups · 8 fresh / 0 reused candidates
Review source reports: none
Evidence triage: 78 deterministic / 8 contextual candidates · 7 contextual / 17 total behavior cases
Model budget: 3 model calls · 7 / 12 fresh cases · 77685 / 200000 estimated input · 72864 / 250000 actual input · 5253 / 40000 output tokens
Review batching: 3 model calls · up to 5 groups and 6 candidates per call · 0 retry calls · 0 over-budget singleton calls
Review usage: 72864 input · 5253 output · 0 cache read · 0 reasoning tokens
Report: 91e1f56c5fe40cc8697b6fc5c92c6dd50526ef619454df51ed60d5c49d508e6a