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

chitienhsiehwork-ai/gu-log

https://github.com/chitienhsiehwork-ai/gu-log · scanned 2026-06-17 01:48 UTC (1 month, 1 week ago)

125 raw signals (0 security + 125 graph)

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

Complete repo analysis

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

JSON
Combined
41.7
/100
Security checks
42
0 findings
System graph
42
100.0% cov · 112 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 20 Medium 64 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 112 Crowd 0 Layer: Software 1 Frontend 5 Network 15 Security 19 Cicd 3 Quality 49 Api 20
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 41.7/100 with 100.0% coverage. It contains 1619 nodes across 19 cross-layer flows, written primarily in mixed languages. Engine surfaced 125 findings — concentrated in quality (49), api (20), security (19). Risk profile is high: 0 critical, 20 high, 66 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 89 of 112 actionable findings. 125 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 api Wiring conf 1.00 Dangling fetch: GET /api/health (sqaa-api/tests/health.test.ts:10)
`sqaa-api/tests/health.test.ts:10` calls `GET /api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/health (sqaa-api/tests/health.test.ts:21)
`sqaa-api/tests/health.test.ts:21` calls `GET /api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/health (sqaa-api/tests/routes.test.ts:119)
`sqaa-api/tests/routes.test.ts:119` calls `GET /api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/health (sqaa-api/tests/routes.test.ts:127)
`sqaa-api/tests/routes.test.ts:127` calls `GET /api/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/health` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/bundle (sqaa-api/tests/routes.test.ts:75)
`sqaa-api/tests/routes.test.ts:75` calls `GET /api/metrics/bundle` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/bundle` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/content (sqaa-api/tests/routes.test.ts:102)
`sqaa-api/tests/routes.test.ts:102` calls `GET /api/metrics/content` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/content` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/coverage (sqaa-api/tests/routes.test.ts:63)
`sqaa-api/tests/routes.test.ts:63` calls `GET /api/metrics/coverage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/coverage` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/dependencies (sqaa-api/tests/routes.test.ts:93)
`sqaa-api/tests/routes.test.ts:93` calls `GET /api/metrics/dependencies` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/dependencies` If this points at an external API, prefix it with `https://` so …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/eslint (sqaa-api/tests/routes.test.ts:42)
`sqaa-api/tests/routes.test.ts:42` calls `GET /api/metrics/eslint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/eslint` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/lighthouse (sqaa-api/tests/routes.test.ts:53)
`sqaa-api/tests/routes.test.ts:53` calls `GET /api/metrics/lighthouse` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/lighthouse` If this points at an external API, prefix it with `https://` so the …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/links (sqaa-api/tests/routes.test.ts:84)
`sqaa-api/tests/routes.test.ts:84` calls `GET /api/metrics/links` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/links` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/overview (sqaa-api/tests/overview.test.ts:12)
`sqaa-api/tests/overview.test.ts:12` calls `GET /api/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/overview` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/overview (sqaa-api/tests/overview.test.ts:22)
`sqaa-api/tests/overview.test.ts:22` calls `GET /api/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/overview` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/overview (sqaa-api/tests/overview.test.ts:37)
`sqaa-api/tests/overview.test.ts:37` calls `GET /api/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/overview` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/overview (sqaa-api/tests/overview.test.ts:48)
`sqaa-api/tests/overview.test.ts:48` calls `GET /api/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/overview` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/overview (sqaa-api/tests/overview.test.ts:59)
`sqaa-api/tests/overview.test.ts:59` calls `GET /api/metrics/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/overview` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/security (sqaa-api/tests/routes.test.ts:12)
`sqaa-api/tests/routes.test.ts:12` calls `GET /api/metrics/security` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/security` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/security/history?limit=5 (sqaa-api/tests/routes.test.ts:31)
`sqaa-api/tests/routes.test.ts:31` calls `GET /api/metrics/security/history?limit=5` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/security/history` If this points at an external API, prefix it wit…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/metrics/security/history?limit=abc (sqaa-api/tests/routes.test.ts:24)
`sqaa-api/tests/routes.test.ts:24` calls `GET /api/metrics/security/history?limit=abc` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/metrics/security/history` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/nonexistent-endpoint (sqaa-api/tests/routes.test.ts:111)
`sqaa-api/tests/routes.test.ts:111` calls `GET /api/nonexistent-endpoint` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/nonexistent-endpoint` If this points at an external API, prefix it with `https://` so…
Dangling fetchHelper:request
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/fetch-chatgpt-share.mjs:258
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/search-test.mjs:248
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 — src/lib/gist-sync.ts:94
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/tribunal-writer.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/tribunal-writer.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/apply.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/opsx/apply.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/archive.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/opsx/archive.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/propose.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/opsx/propose.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/sync.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/opsx/sync.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/playwright-cli/references/element-attributes.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/playwright-cli/references/element-attributes.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/playwright-cli/references/request-mocking.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/playwright-cli/references/request-mocking.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/playwright-cli/references/running-code.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/playwright-cli/references/running-code.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/playwright-cli/references/storage-state.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/playwright-cli/references/storage-state.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/tribunal-monitor/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/tribunal-monitor/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .codex/agents/references/sp-187-v7-false-positive.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.
.codex/agents/references/sp-187-v7-false-positive.md VerificationCodex 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: sources/supergoal/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.
sources/supergoal/SKILL.md VerificationSkill file
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/playwright-cli/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/skills/playwright-cli/SKILL.md:287 Supply chainClaude instruction
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 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
github/codeql-action/init@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/codeql.yml:34, 44 (2 hits)
.github/workflows/nightly-deep.yml:92
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in sources/anthropic/claude-code-dynamic-workflows.html:697
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
sources/anthropic/claude-code-dynamic-workflows.html:697 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/build-version-manifest.mjs:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/build-version-manifest.mjs:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/bundle-budget-check.mjs:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/bundle-budget-check.mjs:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-glossary-links.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-glossary-links.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-jingjing.mjs:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-jingjing.mjs:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-mermaid-visual.mjs:29
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-mermaid-visual.mjs:29 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-translation-pairs.mjs:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-translation-pairs.mjs:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dependency-freshness.mjs:15
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dependency-freshness.mjs:15 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/eval-dedup-harness.mjs:19
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/eval-dedup-harness.mjs:19 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/inject-related-posts.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/inject-related-posts.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/list-content-gate-posts.mjs:2
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/list-content-gate-posts.mjs:2 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/obsidian-import.mjs:45
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/obsidian-import.mjs:45 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/security-gate.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/security-gate.mjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/spark-tribunal-benchmark.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/spark-tribunal-benchmark.mjs:11 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/lib/tribunal-v2/adapters/git.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/lib/tribunal-v2/adapters/git.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/lib/tribunal-v2/runners/claude-cli.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/lib/tribunal-v2/runners/claude-cli.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/lib/tribunal-v2/writer-constraints.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/lib/tribunal-v2/writer-constraints.ts:12 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/tribunal-salvage-from-claude-history.py:205
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 134 placeholder/mock markers across 25 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 10 in use
Port 10 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 13 in use
Port 13 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 14 in use
Port 14 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 16 in use
Port 16 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 18 in use
Port 18 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 21 in use
Port 21 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 23 in use
Port 23 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 40 in use
Port 40 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 42 in use
Port 42 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 45 in use
Port 45 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 46 in use
Port 46 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 51 in use
Port 51 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
medium System graph network Security conf 1.00 Privileged port 52 in use
Port 52 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/cp-candidates-queue.yaml Ports
low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `BASE_URL`, `CI`, `GITHUB_ACTIONS`, `GITHUB_BASE_REF`, `MERMAID_CHECK_MODEL`, `OPENCLAW_MODEL`, `PLAYWRIGHT_BASE_URL` + 1 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 572 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 12 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/cache@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 12 locations
.github/workflows/nightly-deep.yml:25, 38, 55, 72, 101, 119, 149, 171, +1 more (9 hits)
.github/workflows/ci.yml:144, 161 (2 hits)
.github/workflows/deploy-smoke-test.yml:13
CI/CD securitySupply chainGithub actions
low System graph security security conf 1.00 Insecure pattern 'document_write' in sources/anthropic/claude-code-dynamic-workflows.html:28
Found a known-risky pattern (document_write). Review and replace if possible.
sources/anthropic/claude-code-dynamic-workflows.html:28 Document write
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 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 quality Integrity conf 1.00 Old/deprecated-named symbol `isDeprecated` in scripts/dependency-freshness.mjs:69
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 software Dead code conf 1.00 Possibly dead Python function: run_one
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/opus-url-burn-runner.py:221
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/tribunal-v2-run.ts:61
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 — sqaa-api/src/index.ts:13
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 — sqaa-api/src/middleware/logger.ts:28
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/lib/tribunal-v2/adapters/git.ts:133
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/toc-scroll-accuracy.spec.ts:196
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
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/885640df-cf92-403a-8e9e-893ad0012fc0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/885640df-cf92-403a-8e9e-893ad0012fc0/

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.