Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

bloknayrb/tandem

https://github.com/bloknayrb/tandem · scanned 2026-06-17 01:42 UTC (1 month, 1 week ago)

293 raw signals (0 security + 293 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -29.2 (diff) · 289 actionable findings from 1 signal source. 4 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
47.5
/100
Security checks
48
0 findings
System graph
48
100.0% cov · 289 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 25 Medium 42 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 289 Crowd 0 Layer: Frontend 14 Security 23 Cicd 4 Quality 219 Api 29
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 47.5/100 with 100.0% coverage. It contains 3511 nodes across 22 cross-layer flows, written primarily in mixed languages. Engine surfaced 293 findings — concentrated in quality (219), api (29), security (23). Risk profile is high: 1 critical, 25 high, 46 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 105 of 289 actionable findings. 293 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/reviews/pr-578.codex.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/reviews/pr-578.codex.md:374 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/reviews/pr-579.codex.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/reviews/pr-579.codex.md:1079 SecretsClaude instruction
high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/reviews/pr-580.codex.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/reviews/pr-580.codex.md:1273 SecretsClaude instruction
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/info (tests/tauri-driver/specs/prevent-default.e2e.ts:140)
`tests/tauri-driver/specs/prevent-default.e2e.ts:140` calls `GET /api/info` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/info` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${address.port}${url} (tests/server/sessions-routes.test.ts:70)
`tests/server/sessions-routes.test.ts:70` calls `GET http://127.0.0.1:${address.port}${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${DEFAULT_MCP_PORT}${API_INFO} (src/client/hooks/yjsSync.svelte.ts:194)
`src/client/hooks/yjsSync.svelte.ts:194` calls `GET http://127.0.0.1:${DEFAULT_MCP_PORT}${API_INFO}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${mcpPort}/api/events (src/cli/doctor.ts:377)
`src/cli/doctor.ts:377` calls `GET http://127.0.0.1:${mcpPort}/api/events` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/events` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${url} (tests/server/integrations/api-routes.test.ts:129)
`tests/server/integrations/api-routes.test.ts:129` calls `GET http://127.0.0.1:${port}${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${url} (tests/server/launcher/api-routes.test.ts:106)
`tests/server/launcher/api-routes.test.ts:106` calls `GET http://127.0.0.1:${port}${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}${url} (tests/server/models/api-routes.test.ts:92)
`tests/server/models/api-routes.test.ts:92` calls `GET http://127.0.0.1:${port}${url}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource (tests/server/server-security-invariants.test.ts:40)
`tests/server/server-security-invariants.test.ts:40` calls `GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/.well-known/oauth-pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource (tests/server/server-security-invariants.test.ts:64)
`tests/server/server-security-invariants.test.ts:64` calls `GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/.well-known/oauth-pr…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource/mcp (tests/server/server-security-invariants.test.ts:52)
`tests/server/server-security-invariants.test.ts:52` calls `GET http://127.0.0.1:${port}/.well-known/oauth-protected-resource/mcp` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/.well-known/oaut…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/health (tests/server/server-security-invariants.test.ts:102)
`tests/server/server-security-invariants.test.ts:102` calls `GET http://127.0.0.1:${port}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:${port}/health (tests/server/server-security-invariants.test.ts:90)
`tests/server/server-security-invariants.test.ts:90` calls `GET http://127.0.0.1:${port}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` If this points at an external API, prefix …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${address.port}${API_SHUTDOWN} (tests/server/shutdown-route.test.ts:48)
`tests/server/shutdown-route.test.ts:48` calls `POST http://127.0.0.1:${address.port}${API_SHUTDOWN}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${address.port}${API_STORE_RECLAIM_LOCK} (tests/server/store-reclaim-route.test.ts:60)
`tests/server/store-reclaim-route.test.ts:60` calls `POST http://127.0.0.1:${address.port}${API_STORE_RECLAIM_LOCK}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an exte…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${DEFAULT_MCP_PORT}${API_CLOSE} (src/client/hooks/yjsSync.svelte.ts:579)
`src/client/hooks/yjsSync.svelte.ts:579` calls `POST http://127.0.0.1:${DEFAULT_MCP_PORT}${API_CLOSE}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, pref…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${DEFAULT_MCP_PORT}${API_RENAME} (src/client/hooks/yjsSync.svelte.ts:610)
`src/client/hooks/yjsSync.svelte.ts:610` calls `POST http://127.0.0.1:${DEFAULT_MCP_PORT}${API_RENAME}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/<p>` If this points at an external API, pre…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${noTokenPort}/api/rotate-token (tests/server/rotate-token-route.test.ts:179)
`tests/server/rotate-token-route.test.ts:179` calls `POST http://127.0.0.1:${noTokenPort}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/rotate-token (tests/server/rotate-token-route.test.ts:114)
`tests/server/rotate-token-route.test.ts:114` calls `POST http://127.0.0.1:${port}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/rotate-token (tests/server/rotate-token-route.test.ts:132)
`tests/server/rotate-token-route.test.ts:132` calls `POST http://127.0.0.1:${port}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/rotate-token (tests/server/rotate-token-route.test.ts:150)
`tests/server/rotate-token-route.test.ts:150` calls `POST http://127.0.0.1:${port}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/rotate-token (tests/server/rotate-token-route.test.ts:76)
`tests/server/rotate-token-route.test.ts:76` calls `POST http://127.0.0.1:${port}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST http://127.0.0.1:${port}/api/rotate-token (tests/server/rotate-token-route.test.ts:98)
`tests/server/rotate-token-route.test.ts:98` calls `POST http://127.0.0.1:${port}/api/rotate-token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/api/rotate-token` If this points at an external…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/shared/cli-runtime.ts:170
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/diverge-on-call.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/agents/diverge-on-call.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/diverge.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/commands/diverge.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/knowledge-graph/nodes/adr-031.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/knowledge-graph/nodes/adr-031.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/knowledge-graph/nodes/concept-file-watcher.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/knowledge-graph/nodes/concept-file-watcher.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/knowledge-graph/nodes/rule-extract-text-not-markdown.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/knowledge-graph/nodes/rule-extract-text-not-markdown.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/knowledge-graph/nodes/rule-stdout-reserved.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/knowledge-graph/nodes/rule-stdout-reserved.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/notes/pr-review-759-2026-05-18.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/notes/pr-review-759-2026-05-18.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/notes/pr-review-760-2026-05-18.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/notes/pr-review-760-2026-05-18.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/notes/pr-review-761-2026-05-18.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/notes/pr-review-761-2026-05-18.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/notes/pr-review-765-2026-05-18.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/notes/pr-review-765-2026-05-18.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/notes/pr-review-summary-2026-05-18.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/notes/pr-review-summary-2026-05-18.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/reviews/issue-pipeline-skill-plan-review-content.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/reviews/issue-pipeline-skill-plan-review-content.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/reviews/meta-plan.codex.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/reviews/meta-plan.codex.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/screenshots/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/screenshots/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/tandem/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
skills/tandem/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 76, 81
.github/workflows/tauri-release.yml:76, 81 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
3 files, 3 locations
.github/workflows/claude-code-review.yml
.github/workflows/publish.yml
.github/workflows/tauri-release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/server/mcp/server.ts:377
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/server/mcp/server.ts:377 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-system-impl/preview/d5-empty-states.html:121
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-system-impl/preview/d5-empty-states.html:121 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-reaper.mjs:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-reaper.mjs:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/ci/stdio-smoke.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/ci/stdio-smoke.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev-standalone.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dev-standalone.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/download-node-sidecar.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/download-node-sidecar.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/e2e-server.mjs:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/e2e-server.mjs:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/spikes/probe-launcher.mjs:40
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/spikes/probe-launcher.mjs:40 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/spikes/probe-monitor-viability.ts:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/spikes/probe-monitor-viability.ts:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/spikes/probe-session-resume.ts:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/spikes/probe-session-resume.ts:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/spikes/run-docx-export.mjs:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/spikes/run-docx-export.mjs:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/start.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/start.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/cli/uninstall-scrub.ts:39
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/cli/uninstall-scrub.ts:39 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/annotations/process-identity.ts:20
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/annotations/process-identity.ts:20 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/integrations/acl-win.ts:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/integrations/acl-win.ts:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/integrations/install-claude-cli.ts:37
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/integrations/install-claude-cli.ts:37 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/launcher/supervisor.ts:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/launcher/supervisor.ts:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/mcp/launcher.ts:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/mcp/launcher.ts:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server/platform.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server/platform.ts:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 18 placeholder/mock markers across 14 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 38 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `APPDATA`, `CAPTURE_DESIGN_BASELINES`, `CI`, `CLAUDECODE`, `CLAUDE_CODE_SESSION_ID`, `CLAUDE_PLUGIN_OPTION_AUTH_TOKEN`, `CLAUDE_PLUGIN_OPTION_SERVER_URL`, `DEV` + 30 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't …
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 91 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/ci.yml:150
.github/workflows/tauri-release.yml:70
CI/CD securitySupply chainGithub actions
low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ann_legacy` in tests/server/annotations/sync.test.ts:318
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ann_old` in tests/server/event-queue.test.ts:704
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `nOld` in tests/server/issue-377-position-diagnostics.test.ts:308
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `report_v2` in tests/server/file-io/filename-safety.test.ts:13
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `tooOld` in src/server/file-io/doc-backup.ts:459
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `tooOld` in src/server/file-io/reaper.ts:96
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `v1_to_v2` in src/server/annotations/migrations/index.ts:3
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `v1_to_v2` in src/server/annotations/migrations/runner.ts:23
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `v1_to_v2` in src/server/annotations/migrations/v1_to_v2.ts:27
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-keys.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/sign-license.ts:35
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/spikes/probe-monitor-viability.ts:367
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/spikes/probe-session-resume.ts:418
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/cli/index.ts:51
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/crdt/authorship-marks-size.test.ts:120
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/server/annotations/perf.test.ts:129
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/server/authorship-tracking.test.ts:165
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/server/file-opener-edge-cases.test.ts:81
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/server/markdown-roundtrip.test.ts:135
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tests/tauri-driver/specs/prevent-default.e2e.ts:136
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /mcp
`src/server/mcp/server.ts` declares `DELETE /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /mcp
`src/server/mcp/server.ts` declares `GET /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{*path}
`src/server/mcp/server.ts` declares `GET /{*path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /mcp
`src/server/mcp/server.ts` declares `POST /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /webhooks/license
`src/server/mcp/server.ts` declares `POST /webhooks/license` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api
`src/server/mcp/server.ts` declares `USE /api` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /mcp
`src/server/mcp/server.ts` declares `USE /mcp` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src-tauri/src/cowork_installer.rs (1251 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src-tauri/src/lib.rs (3973 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/server/mcp/document-service.ts (1282 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/server/mcp/file-opener.ts (1552 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/e2e/margin-view.spec.ts (1361 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/server/annotations/sync.test.ts (1499 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/7639b1c3-eb2e-43bd-9638-33158cbb7b68/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7639b1c3-eb2e-43bd-9638-33158cbb7b68/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.