doolijb/serene-pub

Scanner reason: JavaScript analysis matched static JavaScript security signal javascript.xray.data-exfiltration. 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.data-exfiltration

File role

production

Source

vitest.setup.ts:22

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

Contextual assessment: The file obtains a session token from a same-origin API endpoint that reads HttpOnly cookies server-side, then passes that token in the Socket.IO auth handshake for a connection made with no URL argument, which Socket.IO resolves to the same origin that served the page. This is a standard pattern for authenticating WebSocket connections when cookies are not otherwise forwarded, and the data flow stays entirely within the application's own server. There is no third-party destination, no storage of the token beyond the connection, and no disclosure outside the connection lifecycle; the same-file co-occurrence of the token source and network sink is inherent to establishing an authenticated socket, not evidence of exfiltration.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

tavernkeeper 5

Rule

credential-exfiltration

File role

production

Source

src/lib/client/sockets/loadSockets.client.ts:11

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

Contextual assessment: Same file as the prior group, flagged by a separate scanner for credential source and network sink in one file. The fetch on line 11 targets the same-origin relative path /api/socket-token with credentials included, which is the standard pattern for retrieving the authenticated user's own socket token from the application backend. The cookie and localStorage reads in the same file are fallback token retrieval paths. No external destination is involved and no exfiltration path is demonstrated.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

tavernkeeper 5

Rule

credential-exfiltration

File role

production

Source

src/lib/client/auth.ts:11

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.dynamic-execution.node-shell. The match applies to this repository.

Contextual assessment: This candidate flags the execSync call at line 264, which runs chmod +x on the macOS app bundle executable script that was just written by fs.writeFileSync at line 261. The path is derived from path.join(macOSDir, 'serene-pub') where macOSDir is built from the script's own __dirname and hardcoded directory names. No untrusted input flows into the command. This is expected behavior for a packaging script that must set executable permissions on generated launcher scripts.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

opengrep 1.26.0

Rule

tavernkeeper.dynamic-execution.node-shell

File role

tooling

Source

scripts/create-executables.js:264

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

Contextual assessment: The file runs dotenv at server startup and fills a small set of framework environment variables (reverse-proxy headers and origin) from operator-provided values, recording which derived keys it applied on a global so the startup banner can report them. Accessing process.env and writing derived values is the declared purpose of this preload module and is disclosed in comments and at startup. No environment contents are transmitted over a network, logged, or persisted outside the process, and only keys the operator already set influence the derivation. The scanner's serialize-environment heuristic matches the benign reading and writing of process.env entries, not an exposure path.

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

production

Source

src/lib/server/config/preloadEnv.js:37

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

Contextual assessment: JS-X-Ray flagged the execSync call at lines 168-171 as an unsafe-command signal. The command string is constructed from nodeMobilePkg, which is a hardcoded string literal (nodejs-mobile-react-native@18.20.4), and tempDir, which is derived from the script's own filesystem location via path.join(rootDir, 'temp-nodejs-mobile'). No user input, external data, or untrusted content flows into the command. This is a build-time tooling script that fetches a specific npm tarball to extract native libraries for Android packaging, running in CI or local developer build contexts. The scanner confidence is low, and the actual data flow shows no injection path.

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.unsafe-command

File role

tooling

Source

scripts/build-android.js:168-171

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

Contextual assessment: The zizmor superfluous-actions info finding flags the use of softprops/action-gh-release@v2 as potentially redundant with runner-included functionality. This is a code-quality hint, not a security vulnerability. The workflow properly narrows permissions to contents:write, passes REF_NAME through an environment variable rather than direct interpolation into run blocks, and uses secrets.GITHUB_TOKEN for release asset uploads. No attacker-controlled input reaches the release action; file paths come from a prior step output derived from a hardcoded version string and CI-produced build artifacts.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

zizmor 1.28.0

Rule

superfluous-actions

File role

tooling

Source

.github/workflows/build-android.yml:145

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

Contextual assessment: The scanner flags co-occurrence of credential-bearing state reads (document.cookie, localStorage) and an outbound fetch in the same file. The fetch targets a same-origin relative endpoint (/api/socket-token) to retrieve the user's own socket authentication token. The cookie and localStorage reads are fallback paths for the same auth token. All data flows remain within the application's own origin and serve the stated multi-user WebSocket authentication purpose. No credentials are transmitted to any external or third-party destination.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

javascript-analysis webcrack-2.16.0_js-x-ray-16.0.0_signatures-1_literals-1_families-1

Rule

javascript.credential-to-network

File role

production

Source

src/lib/client/auth.ts:11-36

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

Contextual assessment: The scanner flagged an obfuscation signal, but the supplied source is a plainly readable Node build script that reads a generated server file, applies documented regex replacements to brand startup messages, injects a startup banner, wires an env preload import, and enables a browser auto-open for a local address. The long runs of unusual characters that likely triggered the heuristic are decorative ASCII art inside string literals, not encoded or concealed payload. There is no data exfiltration, hidden execution, encoded indirection, or destination beyond the local build output; all destinations (localhost and 127.0.0.1) are disclosed and match the stated purpose of launching the packaged app.

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

tooling

Source

scripts/customize-build.js:1

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

Contextual assessment: The zizmor superfluous-actions info finding targets the softprops/action-gh-release@v2 step in the release workflow. This is a quality suggestion, not a security issue. The job scopes permissions to contents:write, uses environment variables (REF_NAME) instead of direct interpolation to prevent script injection, and uses secrets.GITHUB_TOKEN for authenticated release uploads. File inputs are glob patterns matching CI-produced zip artifacts and step outputs from prerelease detection. No untrusted or attacker-controlled data flows into the action inputs in a way that creates concrete harm.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

zizmor 1.28.0

Rule

superfluous-actions

File role

tooling

Source

.github/workflows/release.yml:352

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

Contextual assessment: The scanner flags credential access and network transmission in one file. The credential-bearing state identified is this.connection.baseUrl, which is a user-configured KoboldCPP server URL, not a secret credential. The fetch calls target the user's own KoboldCPP instance to query context limits, send generation requests, and abort in-flight generations. All network destinations are derived from the user's own connection configuration. This is the core functionality of a KoboldCPP connection adapter in an AI roleplay application and matches the project's stated purpose of connecting to local or user-configured LLM backends. No credentials are exfiltrated to any third-party destination.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

tavernkeeper 5

Rule

credential-exfiltration

File role

production

Source

src/lib/server/connectionAdapters/KoboldCppAdapter.ts:116

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

Contextual assessment: The scanner flagged access to process.env as a serialize-environment signal. In the supplied source, process.env is read for two variables: SERENE_PUB_DATA_DIR and VITEST_WORKER_ID. One is then written with a temporary directory path. This is legitimate test infrastructure behavior that redirects test database operations away from real user data. No environment contents are serialized, transmitted, logged, or sent to any external destination. The signal is a false positive on standard test setup configuration.

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

production

Source

vitest.setup.ts:25

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.dynamic-execution.node-shell. The match applies to this repository.

Contextual assessment: OpenGrep matched the execSync call at lines 169-172 for Node process execution. The command interpolates nodeMobilePkg (a hardcoded string constant) and tempDir (a path derived from the script's own directory). Neither value is attacker-controlled or sourced from untrusted input. The script runs as a build tool in CI or local build contexts. This is expected behavior for a build script that invokes npm pack to fetch a specific package tarball.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

opengrep 1.26.0

Rule

tavernkeeper.dynamic-execution.node-shell

File role

tooling

Source

scripts/build-android.js:169-172

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.dynamic-execution.node-shell. The match applies to this repository.

Contextual assessment: This candidate flags the execSync call at line 180, which runs chmod +x on the Linux desktop-shortcut installer script that was just written at line 177. The path is constructed from path.join(platformDir, 'install-desktop-shortcut.sh') using internally-derived directory values. No external or user-controlled input reaches the command string. Making generated install scripts executable is expected behavior for a release packaging tool.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

opengrep 1.26.0

Rule

tavernkeeper.dynamic-execution.node-shell

File role

tooling

Source

scripts/create-executables.js:180

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.dynamic-execution.node-shell. The match applies to this repository.

Contextual assessment: This candidate flags the execSync call at line 201, which runs chmod +x on the Linux executable wrapper script just written at line 198. The path comes from path.join(platformDir, config.executable) where config.executable is the hardcoded string 'Serene Pub'. No untrusted input is involved. Setting executable permissions on a generated launcher is standard and expected for a cross-platform packaging script.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

opengrep 1.26.0

Rule

tavernkeeper.dynamic-execution.node-shell

File role

tooling

Source

scripts/create-executables.js:201

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 a transparent Node.js packaging script that reads package.json, copies a favicon, and writes platform-specific launcher scripts (Windows .bat, Linux shell wrappers, macOS .app bundle). The obfuscation signal is a false positive, most likely triggered by the heavily-escaped sed expression embedded in the generated bash installer (line 153), which contains multiple backslash sequences for desktop-entry escaping. The surrounding code is readable, well-commented, and contains no encoded strings, eval, or hidden control flow. All file paths are derived from the script's own directory and hardcoded config values; no untrusted input is involved.

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

tooling

Source

scripts/create-executables.js:1

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

Contextual assessment: The three execSync calls (lines 180, 201, 264) each run chmod +x on files the script itself just created via fs.writeFileSync. The command arguments are constructed from path.join using the script's own __dirname, hardcoded platform directory names, and hardcoded config values (e.g., 'Serene Pub', 'serene-pub', 'install-desktop-shortcut.sh'). No user-controlled or external input reaches the command string. Running chmod on freshly generated shell scripts is expected and necessary behavior for a cross-platform packaging tool.

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.unsafe-command

File role

tooling

Source

scripts/create-executables.js:179

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.dynamic-execution.node-shell. The match applies to this repository.

Contextual assessment: OpenGrep matched the second execSync call at lines 178-180, which runs tar extraction. The tarball filename is obtained from fs.readdirSync on a temp directory that was just created and populated solely by the preceding npm pack command. The tempDir path is derived from the script's own location. No external or attacker-controlled input reaches this command. The tarball content comes from the official npm registry for a pinned package version. This is expected build-time behavior in a tooling script.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner

opengrep 1.26.0

Rule

tavernkeeper.dynamic-execution.node-shell

File role

tooling

Source

scripts/build-android.js:178-180