TavernKeeper Scan Report

AventurasTeam/Aventuras

Commit b94074c Reviewed Sep 23, 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 89 low

What this review found

No material or immediate-danger item was identified.

Minor cautions

zizmor reported secrets-inherit

Minor caution · high confidence

When a stable release is built, the Android job receives every stored secret rather than just the Android signing ones. Only maintainers can push release tags or start the run, so this is over-sharing within a trusted pipeline.

Technical evidence

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

Contextual assessment: The stable-release pipeline forwards every repository secret to the reusable Android build workflow in the same repository. The Android signing secrets match the signing and upload steps that publish builds, but blanket inheritance also exposes unrelated secrets to that job. The workflow starts only from a stable-version tag push or manual dispatch, both of which require write access, so no attacker-controlled trigger or untrusted data flow is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Pass only the Android signing secrets explicitly to the called workflow.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/release.yml:57

zizmor reported secrets-inherit

Minor caution · high confidence

When a pre-release is built, every stored secret is handed to the Android build job even though it only needs the Android signing ones. Only maintainers can push release tags or start the run, so this is over-sharing within a trusted pipeline.

Technical evidence

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

Contextual assessment: The pre-release pipeline forwards all repository secrets to the reusable Android build workflow in the same repository. The Android signing secrets are proportionate to the signing and upload steps that run when publishing, but blanket inheritance also passes unrelated secrets. The workflow starts only from a version-tag push or manual dispatch, both of which require write access to the repository, so no external attacker trigger or untrusted data flow is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Forward only the Android signing secrets explicitly to the called workflow instead of inheriting everything.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/pre-release.yml:58

zizmor reported superfluous-actions

Minor caution · high confidence

The release pipeline leans on an outside helper for something GitHub's built-in tools can do. Dropping the helper would shrink the fallout if it were ever compromised, but nothing here shows misuse.

Technical evidence

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

Contextual assessment: The draft-release creation step uses a third-party release action while the runner's built-in command-line tooling offers the same capability. The avoidable dependency sits in a pipeline with write access and access to inherited signing material. The workflow triggers only on stable-version tags or manual dispatch, and the supplied evidence shows no exfiltration or untrusted input, so this remains a supply-chain hygiene finding without demonstrated exposure.

Impact: low · Exploitability: unlikely

Developer action: Replace the action with native release commands, or pin it to a full commit hash rather than a floating tag.

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

zizmor reported secrets-inherit

Minor caution · high confidence

The main build pipeline hands every stored secret to the Android build job even though that job only needs the Android signing secrets. Only maintainers can start these builds, so this is a tidiness issue rather than a live danger.

Technical evidence

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

Contextual assessment: The orchestrating CI workflow forwards the repository's entire secret set to the reusable Android build workflow. That build legitimately needs the Android signing material even in cache-warming runs because artifacts are deliberately signed, but blanket inheritance also hands over secrets the Android leg never uses. Triggers are restricted to a weekly schedule, filtered pushes to the default branch, and manual dispatch, all of which require write access, so no attacker-controlled trigger path is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Replace blanket secret inheritance with explicit forwarding of only the Android signing secrets the called workflow actually consumes.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/ci.yml:59

zizmor reported unsound-ternary

Minor caution · high confidence

A clever one-line shortcut meant to leave release notes alone on a re-run does not actually work: the default note text always wins, so any notes a maintainer typed into the draft can be replaced. It is an annoying bug in the release script, not a security hole.

Technical evidence

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

Contextual assessment: The release-body input uses logical operators to emulate a conditional. Because the intended empty-string branch is falsy in the workflow expression language, the fallback text is selected in every case, including re-runs where an existing draft already contains hand-edited notes. The documented intent of preserving typed notes on re-run therefore fails, and those notes can be overwritten. This is a self-inflicted automation correctness defect with recoverable loss of typed text; there is no attacker-controlled path, secret exposure, or user-facing harm demonstrated.

Impact: low · Exploitability: plausible

Developer action: Compute the release body in a preceding script step that emits an empty value on re-run, or gate the input with a genuine conditional, and verify the re-run scenario with a test.

Scanner: zizmor 1.28.0
Rule: unsound-ternary
File role: tooling
Source: .github/workflows/pre-release.yml:46

Gitleaks reported generic-api-key

Minor caution · high confidence

The flagged string is a search key for a public character-directory website, the same key that website hands to every visitor's browser. It is not the app's own password and cannot reach anything belonging to the user; it just looks like a leaked secret to scanning tools.

Technical evidence

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

Contextual assessment: The flagged constant is a fallback bearer token for a third-party character-search API used by the discovery feature. The surrounding code shows the primary path fetches this same token by scraping the provider's public client-side configuration script, which the provider serves to every browser visitor, so the constant is a public client identifier rather than a private project credential. It authorizes only search queries against that third-party service, is unrelated to this application's users, their stories, or their model-provider keys, and no concrete harm to users is demonstrated. The residual issues are hygiene: a secret-shaped literal in source that trips scanners, potential reliance on a token the provider can rotate, and downstream host allow-listing that appropriately constrains fetched content.

Impact: low · Exploitability: unlikely

Developer action: Document the value as a public client token with a scanner allowlist annotation, and prefer shipping only the dynamic token-fetch path so provider rotation degrades gracefully instead of depending on a stale constant.

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

zizmor reported superfluous-actions

Minor caution · high confidence

The build recipe borrows a community helper tool to publish releases when GitHub's own built-in tools could do the same job. Relying on fewer outside helpers slightly shrinks the surface for a compromised helper to misuse the pipeline, but nothing here shows any actual harm.

Technical evidence

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

Contextual assessment: The flagged step uses a popular third-party release action to create a draft release and attach the built artifact. The audit rule notes that the hosted runner's built-in command-line tooling can already do this, so the action is an avoidable supply-chain dependency. The reusable workflow is invoked only from tag-triggered or default-branch pipelines under maintainer control, and the supplied evidence shows no untrusted trigger, no exfiltration, and no obfuscation. The finding is release-automation hygiene, not demonstrated exposure.

Impact: low · Exploitability: unlikely

Developer action: Prefer the runner's native release commands for draft creation and asset upload, or if the action is kept, pin it to a full commit hash rather than a floating major tag.

Scanner: zizmor 1.28.0
Rule: superfluous-actions
File role: tooling
Source: .github/workflows/build-android.yml:149

zizmor reported secrets-inherit

Minor caution · high confidence

The desktop build job also receives every stored secret when it only needs a few of them. Since only maintainers can trigger these runs, this is over-sharing inside a trusted pipeline rather than an open door.

Technical evidence

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

Contextual assessment: The same blanket inheritance passes all repository secrets to the reusable desktop build workflow in the same repository. The desktop leg needs only its own signing or packaging material, so more secrets are exposed to that job than its purpose requires. The workflow runs only on schedule, on filtered default-branch pushes, or by manual dispatch, and the called workflows are first-party files reviewed alongside this evidence; no untrusted input or attacker-controlled activation is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Pass only the specific desktop-build secrets explicitly instead of inheriting the full secret set.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/ci.yml:52

zizmor reported secrets-inherit

Minor caution · high confidence

The desktop build job for stable releases receives every stored secret when only a subset is relevant. Only maintainers can start it, so this is over-sharing inside a trusted pipeline.

Technical evidence

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

Contextual assessment: The stable-release pipeline also forwards all repository secrets to the reusable desktop build workflow in the same repository, more than that job's packaging steps require. Triggering requires a stable-version tag push or manual dispatch, both write-access operations. The called workflow is first-party and reviewed alongside this evidence, and no untrusted input or attacker-controlled activation is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Forward only the desktop-build secrets the called workflow actually consumes.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/release.yml:49

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: tooling
Source: scripts/version.js:14

zizmor reported superfluous-actions

Minor caution · high confidence

The release pipeline uses an outside helper for a job GitHub's own tools can already do. Cutting outside helpers reduces the fallout if that helper were ever compromised, but nothing here indicates any problem today.

Technical evidence

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

Contextual assessment: The draft-creation step uses a third-party release action although the runner's built-in command-line tooling provides equivalent functionality. This is an avoidable external dependency in a pipeline that holds write access and signing material. The workflow triggers only on version tags or manual dispatch under maintainer control, and the supplied evidence shows no exfiltration or untrusted input, so the finding is supply-chain hygiene rather than demonstrated exposure.

Impact: low · Exploitability: unlikely

Developer action: Use the runner's native release commands, or pin the action to a full commit hash instead of a floating tag.

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

zizmor reported secrets-inherit

Minor caution · high confidence

The desktop build job for pre-releases also receives every stored secret when only a few are relevant. Only maintainers can start it, so this is over-sharing inside a trusted pipeline.

Technical evidence

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

Contextual assessment: The pre-release pipeline forwards all repository secrets to the reusable desktop build workflow in the same repository. Only the desktop packaging or signing material is proportionate to that job's steps. Triggering requires pushing a version tag or manual dispatch, both write-access operations, so the over-sharing is confined to maintainer-initiated runs and no attacker-controlled activation or untrusted data flow is demonstrated.

Impact: low · Exploitability: unlikely

Developer action: Forward only the desktop-build secrets the called workflow needs instead of inheriting the full set.

Scanner: zizmor 1.28.0
Rule: secrets-inherit
File role: tooling
Source: .github/workflows/pre-release.yml:50

zizmor reported unsound-ternary

Minor caution · high confidence

A one-line shortcut meant to keep existing release notes on a re-run always picks the default note instead, so notes typed into a draft can be overwritten. It is a scripting bug, not a security hole.

Technical evidence

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

Contextual assessment: The release-body input emulates a conditional with logical operators. Because the intended empty-string branch is falsy in the workflow expression language, the fallback body text is chosen in every run, including re-runs against an existing draft whose notes were typed by hand. The stated intent of preserving those notes therefore fails, and the loss is limited to overwritten draft text. No attacker-controlled path, secret exposure, or user-facing harm is demonstrated; this is an automation correctness defect.

Impact: low · Exploitability: plausible

Developer action: Set the body from a preceding script step that emits an empty value on re-run, or use a real conditional, and test the re-run path.

Scanner: zizmor 1.28.0
Rule: unsound-ternary
File role: tooling
Source: .github/workflows/release.yml:45

Deterministic technical evidence (75)

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/pre-release.yml:24
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/build-desktop.yml:105
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/build-android.yml:149
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:23
zizmor reported template-injection · 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/actions/build-version/action.yml:37
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/build-desktop.yml:83
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
Dependency advisory RUSTSEC-2026-0258:pkg:222a355a74aca3bba6fbb9da 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/build-android.yml:39
zizmor reported artipacked · 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:22-23
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/actions/npm-install/action.yml:34
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 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/build-android.yml:48
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
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/build-android.yml:109
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/build-android.yml:71
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:10
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:24
zizmor reported artipacked · 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/pre-release.yml:23-24
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 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/build-android.yml:66
zizmor reported artipacked · 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/build-android.yml:24-25
Dependency advisory GHSA-9rgm-9g3h-6x36:pkg:8a05d6d431ec29dc9927e432 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-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
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/pre-release.yml:39
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
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
Dependency advisory RUSTSEC-2026-0258:pkg:95f9173f3d1ac6374e456fa8 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/build-android.yml:55
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/build-android.yml:48
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 artipacked · 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/build-desktop.yml:76-80
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/actions/npm-install/action.yml:47
Dependency advisory GHSA-2v37-7h3g-55p8:pkg:06ad0185911f4bb6106d61dc 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-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
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/build-desktop.yml:77
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
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/lib/services/syncActions.test.ts:15
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/build-android.yml:138
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
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/build-desktop.yml:114
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/build-android.yml:25
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
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/actions/npm-install/action.yml:20
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/pre-release.yml:10
Dependency advisory RUSTSEC-2026-0285:pkg:08db2c0c1ca8ee1872b3d40f 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
Dependency advisory GHSA-82fw-gwwq-j7x9:pkg:e73b265e463302d69e55909b 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-0293:pkg:8490244dc01980c032c6e3d6 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 artipacked · 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:23-24
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
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/build-desktop.yml:132
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:38
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/build-android.yml:66
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
Dependency advisory GHSA-4mjr-xmp4-gh2g:pkg:71d1998e85e0b475b0071821 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-82fw-gwwq-j7x9:pkg:00f885f51d12cc13a66b964f 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-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 template-injection · 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/build-android.yml:96

Contextual expected matches (1)

Credential access and network transmission in one file

Expected behavior · high confidence

This is a developer-only test that checks public character-card websites still work with the app's downloader. The alert fired simply because the file mentions reading a file and making a network request in the same place. In reality the test downloads a sample public character and checks it can be read; it never touches passwords, API keys, or personal data, and the whole test is skipped unless a developer deliberately switches it on.

Technical evidence

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

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

Impact: none · Exploitability: unlikely

Developer action: none

Scanner: tavernkeeper 5
Rule: credential-exfiltration
File role: test
Source: src/lib/services/discovery/providers/providers.live.test.ts:12

Coverage and limitations

Inventory: 930 files · 10570858 bytes
Contextual coverage: 89 of 89 candidates assessed

JavaScript coverage

Status: Incomplete
Candidates: 485 files · 3463176 bytes
X-Ray review families: 4 warning occurrences compacted to 4 evidence-preserving review families
Representations: 485 raw · 23 decoded · 0 normalized · 0 bundle modules
Stage scans: 485 raw signatures · 74 raw AST · 485 raw OpenGrep · 23 derived signatures · 0 derived AST · 23 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/story/genreColors.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/drawer/swipe-guard.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.test.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/activity/duration.test.ts — raw-ast / parse
src/lib/services/activity/duration.ts — raw-ast / parse
src/lib/services/activity/index.ts — raw-ast / parse
src/lib/services/activity/recorder.test.ts — raw-ast / parse
src/lib/services/activity/recorder.ts — raw-ast / parse
src/lib/services/activity/reporter.ts — raw-ast / parse
src/lib/services/activity/retention.test.ts — raw-ast / parse
src/lib/services/activity/retention.ts — raw-ast / parse
src/lib/services/activity/trackPhase.test.ts — raw-ast / parse
src/lib/services/activity/trackPhase.ts — raw-ast / parse
src/lib/services/activity/tree.test.ts — raw-ast / parse
src/lib/services/activity/tree.ts — raw-ast / parse
src/lib/services/activity/types.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.test.ts — raw-ast / parse
src/lib/services/ai/image/InlineImageTracker.ts — raw-ast / parse
src/lib/services/ai/image/imageUtils.test.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/image/stylePrompt.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/retrievalSteps.test.ts — raw-ast / parse
src/lib/services/ai/retrieval/retrievalSteps.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

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: b94074c7ca593e15f07d552aa1620019c5eefd62
Completed: Sep 23, 2026
History depth: 9 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: 6 fresh / 0 reused groups · 13 fresh / 0 reused candidates
Review source reports: none
Evidence triage: 76 deterministic / 13 contextual candidates · 6 contextual / 21 total behavior cases
Model budget: 2 model calls · 6 / 12 fresh cases · 64536 / 200000 estimated input · 49849 / 250000 actual input · 11266 / 40000 output tokens
Review batching: 2 model calls · up to 5 groups and 12 candidates per call · 0 retry calls · 0 over-budget singleton calls
Review usage: 49849 input · 11266 output · 0 cache read · 6231 reasoning tokens
Report: 442754efbf8003d84c38203b3b050ff9ac5574a3b76b3decd83c45b0c58e3365