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

romaine-life/tank-operator

https://github.com/romaine-life/tank-operator · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

209 raw signals (0 security + 209 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 172 actionable findings from 1 signal source. 37 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
57.9
/100
Security checks
58
0 findings
System graph
58
100.0% cov · 172 findings
Critical
0
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 0 High 1 Medium 25 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 172 Crowd 0 Layer: Software 3 Frontend 10 Hardware 7 Security 12 Cicd 4 Quality 136
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 57.9/100 with 100.0% coverage. It contains 3302 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 209 findings — concentrated in quality (138), cicd (35), security (12). Risk profile is high: 0 critical, 1 high, 48 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 70 of 172 actionable findings. 209 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 cicd CI/CD security conf 1.00 GitHub Action tracks a moving branch
romaine-life/pipeline-templates/.github/workflows/tofu-plan-apply-template.yml@main can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/tofu.yml:34 CI/CD securitySupply chainGithub actions
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/App.tsx:10564
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/App.tsx:15706
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/auth.ts:54
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — runner-shared/backgroundTaskWake.js:22
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — runner-shared/runtimeConfig.js:15
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — runner-shared/scheduledWakeup.js:15
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — runner-shared/sessionBus.js:247
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/check-removed-chat-runtime.mjs:760
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 instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. 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 18 occurrences GitHub Action is tag-pinned rather than SHA-pinned
azure/login@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 18 locations
.github/workflows/docker-build-check.yaml:123, 127, 169, 185 (4 hits)
.github/workflows/agent-container-build.yml:38, 48, 81 (3 hits)
.github/workflows/api-proxy-build.yml:31, 41, 74 (3 hits)
.github/workflows/mcp-auth-proxy-build.yml:67, 77, 114 (3 hits)
.github/workflows/session-images-build.yml:82, 92, 131 (3 hits)
.github/workflows/build.yml:36, 78 (2 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 7 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.
7 files, 7 locations
.github/workflows/agent-container-build.yml
.github/workflows/api-proxy-build.yml
.github/workflows/build.yml
.github/workflows/docker-build-check.yaml
.github/workflows/mcp-auth-proxy-build.yml
.github/workflows/session-images-build.yml
.github/workflows/tofu.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/App.tsx:10564
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/App.tsx:10564 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/features/transcript/ask-user-question-turn-flow.html:537
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/features/transcript/ask-user-question-turn-flow.html:537 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/features/transcript/background-wake-turn-flow.html:682
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/features/transcript/background-wake-turn-flow.html:682 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in claude-runner/src/cliVersion.ts:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
claude-runner/src/cliVersion.ts:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in codex-runner/src/appServerTransport.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
codex-runner/src/appServerTransport.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-claude-agent-authority.mjs:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-claude-agent-authority.mjs:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-context-window-table-migration.mjs:32
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-context-window-table-migration.mjs:32 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-session-pod-hot-swap-migration.mjs:34
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-session-pod-hot-swap-migration.mjs:34 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-session-readonly-rbac.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-session-readonly-rbac.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-stop-request-migration.mjs:25
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-stop-request-migration.mjs:25 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-tank-http-route-security.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-tank-http-route-security.mjs:3 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 357 placeholder/mock markers across 56 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 Debug conf 1.00 Debug logging residue appears in source files
Found 78 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: alpine:3.20
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:27 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.26-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:14 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: golang:1.26-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
claude-container/Dockerfile:9 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/playwright:v1.49.1-noble
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
agent-container/Dockerfile:10 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 4 locations
claude-container/Dockerfile:20, 35, 49 (3 hits)
Dockerfile:2
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
claude-container/mcp-auth-proxy/Dockerfile:15 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 14, 108
api-proxy/Dockerfile:14, 108 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 9 locations
.github/workflows/session-images-build.yml:51, 148, 174, 179 (4 hits)
.github/workflows/agent-container-build.yml:35
.github/workflows/api-proxy-build.yml:26
.github/workflows/docker-build-check.yaml:86
.github/workflows/mcp-auth-proxy-build.yml:39
.github/workflows/pr-feature-contracts.yml:15
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 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api-proxy/src/tank_api_proxy/metrics.py:handler, api-proxy/src/tank_api_proxy/metrics.py:handler This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're se…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: handler
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api-proxy/src/tank_api_proxy/metrics.py:271
low System graph software Dead code conf 1.00 Possibly dead Python function: handler
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
claude-container/mcp-auth-proxy/src/mcp_auth_proxy/server.py:4357
low System graph software Dead code conf 1.00 Possibly dead Python function: Process
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api-proxy/src/tank_api_proxy/server.py:392
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — claude-runner/src/index.ts:18
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 — claude-runner/src/runner.ts:332
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 — codex-runner/src/index.ts:26
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 — codex-runner/src/runner.ts:1350
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 — frontend/src/chatScrollTelemetry.ts:102
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 — frontend/src/LongChatDebugPage.tsx:456
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 — frontend/src/longTaskTelemetry.ts:183
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 — frontend/src/sessionEventStreamTelemetry.ts:96
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 — frontend/src/sessionListTelemetry.ts:44
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 quality Complexity conf 1.00 Very large file: api-proxy/src/tank_api_proxy/server.py (1119 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/control_actions.go (1749 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/control_actions_test.go (1490 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/handlers_turns.go (1358 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/handlers_turns_test.go (1701 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/observability.go (2947 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/transcript_projection.go (3068 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/cmd/tank-operator/transcript_projection_test.go (1913 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/internal/pgstore/migrations.go (2276 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/internal/sessionmodel/sessionmodel.go (1485 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend-go/internal/store/session_events.go (1380 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: claude-container/mcp-auth-proxy/src/mcp_auth_proxy/server.py (4816 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: claude-container/mcp-auth-proxy/tests/test_server.py (1899 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: claude-runner/src/runner.test.ts (2283 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: claude-runner/src/runner.ts (3415 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: codex-runner/src/runner.ts (1943 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/App.tsx (26763 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/migrationPolicy.test.ts (1591 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/check-removed-chat-runtime.mjs (932 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/check-stop-request-migration.mjs (1300 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/8a01793e-412c-4611-8d22-7a7707b5511b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8a01793e-412c-4611-8d22-7a7707b5511b/

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.