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

zhebinliu/knowledge-base

https://github.com/zhebinliu/knowledge-base · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

317 raw signals (5 security + 312 graph)

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

Complete repo analysis

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

JSON
Combined
57.6
/100
Security checks
58
5 findings
System graph
58
100.0% cov · 252 findings
Critical
2
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 2 High 26 Medium 61 Low 116 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 252 Crowd 0 Layer: Quality 75 Security 57 Software 17 Frontend 47 Hardware 6 Cicd 3 Api 52
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.6/100 with 100.0% coverage. It contains 4558 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 312 findings — concentrated in quality (113), security (57), api (52). Risk profile is high: 2 critical, 25 high, 97 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 203 of 257 actionable findings. 321 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.

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: zhebinliu/knowledge-base
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in scripts/take-screenshots.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 57, 116
scripts/take-screenshots.js:57, 116 (2 hits)
high Security checks quality Practices conf 0.84 Foundry mined bad chains: zhebinliu/knowledge-base
Comment chain pattern product: bad_chains Repo: zhebinliu/knowledge-base Thread: zhebinliu/knowledge-base#5 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, s…
high System graph quality Integrity conf 1.00 Blocking `httpx.post(...)` inside `async def main` — scripts/bootstrap.py:178
Sync I/O inside an async function blocks the event loop. While `httpx.post(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
scripts/bootstrap.py:178 Sync io in asyncPerformance
high System graph api Wiring conf 1.00 Dangling fetch: GET /version.json?t=${Date.now()} (frontend/src/components/VersionWatcher.tsx:32)
`frontend/src/components/VersionWatcher.tsx:32` calls `GET /version.json?t=${Date.now()}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/version.json` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/challenge/run-stream (frontend/src/pages/Challenge.tsx:125)
`frontend/src/pages/Challenge.tsx:125` calls `POST /api/challenge/run-stream` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/challenge/run-stream` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_api_key` without auth dependency — backend/api/agent_settings.py:148
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:148 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_model` without auth dependency — backend/api/agent_settings.py:56
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_routing` without auth dependency — backend/api/agent_settings.py:95
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:95 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `reset_embedding_config` without auth dependency — backend/api/agent_settings.py:438
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:438 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `reset_rerank_config` without auth dependency — backend/api/agent_settings.py:471
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:471 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_model` without auth dependency — backend/api/agent_settings.py:44
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `force_seed` without auth dependency — backend/api/agent_settings.py:257
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:257 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_meeting` without auth dependency — backend/api/meeting.py:1645
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/meeting.py:1645 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_meeting` without auth dependency — meeting/backend/api/meeting.py:1645
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
meeting/backend/api/meeting.py:1645 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `invalidate_cache` without auth dependency — backend/api/agent_settings.py:264
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:264 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mcp_endpoint` without auth dependency — backend/api/mcp.py:653
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/mcp.py:653 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_prompt` without auth dependency — backend/api/agent_settings.py:232
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:232 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sso_bind` without auth dependency — backend/api/auth.py:224
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/auth.py:224 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_api_key` without auth dependency — backend/api/agent_settings.py:141
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:141 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_embedding_config` without auth dependency — backend/api/agent_settings.py:421
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:421 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_model` without auth dependency — backend/api/agent_settings.py:37
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_output_agent` without auth dependency — backend/api/agent_settings.py:360
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:360 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_prompt` without auth dependency — backend/api/agent_settings.py:214
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:214 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_rerank_config` without auth dependency — backend/api/agent_settings.py:455
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:455 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_routing` without auth dependency — backend/api/agent_settings.py:83
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:83 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_task_params` without auth dependency — backend/api/agent_settings.py:179
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agent_settings.py:179 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in frontend/public/estimate/index.html:213
Found a known-risky pattern (new_function_used). Review and replace if possible.
frontend/public/estimate/index.html:213 New function used
medium Security checks quality Practices conf 0.62 4 occurrences Foundry mined assumption checks: zhebinliu/knowledge-base
Comment chain pattern product: assumption_checks Repo: zhebinliu/knowledge-base Thread: zhebinliu/knowledge-base#4 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_g…
4 occurrences
repo-level (4 hits)
medium Security checks quality maintenance conf 0.70 Foundry mined blueprint gap alignment: zhebinliu/knowledge-base
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
medium Security checks quality Practices conf 0.70 2 occurrences Foundry mined unresolved feedback: zhebinliu/knowledge-base
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
2 occurrences
repo-level (2 hits)
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/markdown/ReportMarkdown.tsx:222
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/pages/Challenge.tsx:125
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/pages/console/ConsoleProjectDetail.tsx:1487
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/redesign/console/ConsoleProjectDetail.tsx:1614
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/demo-video/lib/auth.js:27
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/take-screenshots.js:113
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/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: backend/prompts/sharedev/skills/sharedev-apl-code-review/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.
backend/prompts/sharedev/skills/sharedev-apl-code-review/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-apl-lite/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.
backend/prompts/sharedev/skills/sharedev-apl-lite/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-auto/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.
backend/prompts/sharedev/skills/sharedev-auto/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-pwc-execute-plans/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.
backend/prompts/sharedev/skills/sharedev-pwc-execute-plans/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-pwc-finish-development/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.
backend/prompts/sharedev/skills/sharedev-pwc-finish-development/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-pwc-review-code/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.
backend/prompts/sharedev/skills/sharedev-pwc-review-code/SKILL.md VerificationSkill file
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/prompts/sharedev/skills/sharedev-pwc-subagent-driven-development/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.
backend/prompts/sharedev/skills/sharedev-pwc-subagent-driven-development/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 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 hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 26 occurrences Frontend route `/ds` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
26 occurrences
repo-level (26 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 13 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/setup-buildx-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 13 locations
.github/workflows/deploy-prod.yml:157, 159, 167, 176, 189, 198, 225 (7 hits)
.github/workflows/deploy-uat.yml:66, 69, 77, 86, 114 (5 hits)
.github/workflows/desktop-build.yml:80
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/deploy-prod.yml
.github/workflows/deploy-uat.yml
.github/workflows/desktop-build.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/markdown/ReportMarkdown.tsx:222
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/markdown/ReportMarkdown.tsx:222 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson01/demo.html:667
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson01/demo.html:667 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson02/demo.html:974
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson02/demo.html:974 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson03/demo.html:841
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson03/demo.html:841 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson04/demo.html:973
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson04/demo.html:973 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson05/demo.html:940
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson05/demo.html:940 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson06/demo.html:1055
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson06/demo.html:1055 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson07/demo.html:1268
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson07/demo.html:1268 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson08/demo.html:1106
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson08/demo.html:1106 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson09/demo.html:1210
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson09/demo.html:1210 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson10/demo.html:1318
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson10/demo.html:1318 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson11/demo.html:1194
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson11/demo.html:1194 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson12/demo.html:1389
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson12/demo.html:1389 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson13/demo.html:1519
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson13/demo.html:1519 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson14/demo.html:1311
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson14/demo.html:1311 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson15/demo.html:1665
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson15/demo.html:1665 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson16/demo.html:1738
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson16/demo.html:1738 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson17/demo.html:1913
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson17/demo.html:1913 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson18/demo.html:1204
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson18/demo.html:1204 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson19/demo.html:1304
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson19/demo.html:1304 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson20/demo.html:1550
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson20/demo.html:1550 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson21/demo.html:1420
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson21/demo.html:1420 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson22/demo.html:1270
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson22/demo.html:1270 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/lesson23/demo.html:1517
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/lesson23/demo.html:1517 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/player.html:1237
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/player.html:1237 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/quiz.html:701
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/quiz.html:701 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/public/course/script.html:263
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/public/course/script.html:263 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in presentation.html:705
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
presentation.html:705 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in todo-kanban-prototype.html:607
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
todo-kanban-prototype.html:607 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in frontend/public/course/lesson17/demo.html:1950
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
frontend/public/course/lesson17/demo.html:1950 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/demo-video/lib/auth.js:43
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/demo-video/lib/auth.js:43 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in scripts/take-screenshots.js:70
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
scripts/take-screenshots.js:70 Local storage auth token
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/demo-video/narration/tts.py:69
`requests.post(...)` 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 233 placeholder/mock markers across 72 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 quality Tests conf 1.00 Very low test-to-source ratio
7 test file(s) for 443 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/components/console/research/ResearchQuestionnaire.tsx:490
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/components/console/research/ResearchWorkspace.tsx:770
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 16 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DEMO_BUNDLE_ID`, `DEMO_PROJECT_ID`, `DEMO_PROJECT_NAME`, `KB_BASE_URL`, `KB_PASSWORD`, `KB_USERNAME`, `LANG`, `LC_ALL` + 8 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 132 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: nginx:1.27-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:24 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 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.
frontend/Dockerfile:4 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/deploy.yml:85, 101 (2 hits)
.github/workflows/desktop-build.yml:45, 55 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 17 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: meeting/backend/models/markup_template.py:to_dict, backend/models/markup_template.py:to_dict 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 separa…
17 occurrences
repo-level (17 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: meeting/backend/api/feishu_credentials.py:put_feishu_credentials, meeting/backend/api/meeting.py:put_feishu_credentials, backend/api/feishu_credentials.py:put_feishu_credentials, backend/api/meeting.py:put_feishu_credentials This is *the* AI-coder fa…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: meeting/backend/api/markup_template.py:render_template_with_meeting, meeting/backend/api/markup_template.py:export_template_docx, meeting/backend/api/markup_template.py:export_template_md, backend/api/markup_template.py:render_template_with_meeting T…
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 quality Integrity conf 1.00 Old/deprecated-named symbol `insight_v2` in backend/api/briefs.py:26
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 `insight_v2` in backend/scripts/migrate_v3_rename.py:6
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 `isLegacy` in frontend/src/components/TemplateSelector.tsx:31
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 `isLegacy` in frontend/src/redesign/console/TemplateManager.tsx: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 quality Integrity conf 1.00 Old/deprecated-named symbol `isLegacy` in meeting/frontend/src/components/TemplateSelector.tsx:31
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 `isLegacy` in meeting/frontend/src/redesign/console/TemplateManager.tsx: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 quality Integrity conf 1.00 Old/deprecated-named symbol `survey_v2` in frontend/src/pages/Demo.tsx:667
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 software Dead code conf 1.00 Possibly dead Python function: bootstrap_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/qixin_gateway/connection_manager.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_expired_captchas
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/security/captcha.py:118
low System graph software Dead code conf 1.00 Possibly dead Python function: critical_modules_for_industry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agentic/insight_modules.py:552
low System graph software Dead code conf 1.00 Possibly dead Python function: critical_outline_modules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agentic/outline_modules.py:315
low System graph software Dead code conf 1.00 Possibly dead Python function: dep
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/project_acl.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: evaluate_password_checks
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/security/password_policy.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_survey_for_role
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agentic/runner.py:1732
low System graph software Dead code conf 1.00 Possibly dead Python function: has_web_search_provider_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/web_search_service.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: list_connected
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/qixin_gateway/connection_manager.py:144
low System graph software Dead code conf 1.00 Possibly dead Python function: list_outline_modules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agentic/outline_modules.py:310
low System graph software Dead code conf 1.00 Possibly dead Python function: prepend_revision_memories_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/revision_learning.py:203
low System graph software Dead code conf 1.00 Possibly dead Python function: repl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agentic/executor.py:328
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/auth.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: run_challenge_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/challenger_agent.py:595
low System graph software Dead code conf 1.00 Possibly dead Python function: stop_all
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/qixin_gateway/connection_manager.py:136
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_action_items_to_bitable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
meeting/backend/services/meeting/feishu.py:774
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_and_consume
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/security/invite_code.py:88
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 — desktop/src/renderer.ts:31
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/pages/console/ConsoleMeetingDetail.tsx:1373
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 — meeting/frontend/src/pages/console/ConsoleMeetingDetail.tsx:1373
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/demo-video/lib/cursor.js:74
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/demo-video/lib/narration.js:34
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/demo-video/lib/render.js:27
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/demo-video/record-demo.js:50
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/take-screenshots.js: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 api Wiring conf 1.00 Unused endpoint: DELETE /credentials
`meeting/backend/api/feishu_credentials.py` declares `DELETE /credentials` 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: DELETE /feishu-credentials
`meeting/backend/api/meeting.py` declares `DELETE /feishu-credentials` 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: DELETE /{meeting_id}
`meeting/backend/api/meeting.py` declares `DELETE /{meeting_id}` 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: DELETE /{meeting_id}/requirements/{req_id}
`meeting/backend/api/meeting.py` declares `DELETE /{meeting_id}/requirements/{req_id}` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{template_id}
`meeting/backend/api/markup_template.py` declares `DELETE /{template_id}` 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 /
`meeting/backend/api/template.py` declares `GET /` 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 /active
`meeting/backend/api/template.py` declares `GET /active` 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 /credentials
`meeting/backend/api/feishu_credentials.py` declares `GET /credentials` 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 /feishu-credentials
`meeting/backend/api/meeting.py` declares `GET /feishu-credentials` 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 /illustration-styles
`meeting/backend/api/meeting.py` declares `GET /illustration-styles` 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 /placeholders
`meeting/backend/api/markup_template.py` declares `GET /placeholders` 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 /{meeting_id}
`meeting/backend/api/meeting.py` declares `GET /{meeting_id}` 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 /{meeting_id}/audio
`meeting/backend/api/meeting.py` declares `GET /{meeting_id}/audio` 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 /{meeting_id}/export-docx
`meeting/backend/api/meeting.py` declares `GET /{meeting_id}/export-docx` 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 /{meeting_id}/requirements
`meeting/backend/api/meeting.py` declares `GET /{meeting_id}/requirements` 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 /{template_id}
`meeting/backend/api/template.py` declares `GET /{template_id}` 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: PATCH /{meeting_id}
`meeting/backend/api/meeting.py` declares `PATCH /{meeting_id}` 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: PATCH /{meeting_id}/requirements/{req_id}
`meeting/backend/api/meeting.py` declares `PATCH /{meeting_id}/requirements/{req_id}` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /{template_id}
`meeting/backend/api/markup_template.py` declares `PATCH /{template_id}` 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 /
`meeting/backend/api/template.py` declares `POST /` 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 /evolve
`meeting/backend/api/template.py` declares `POST /evolve` 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 /from-text
`meeting/backend/api/meeting.py` declares `POST /from-text` 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 /upload
`meeting/backend/api/markup_template.py` declares `POST /upload` 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 /{meeting_id}/actions/extract_illustrations
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/extract_illustrations` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/actions/extract_process_flows
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/extract_process_flows` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/actions/extract_requirements
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/extract_requirements` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/actions/extract_stakeholders
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/extract_stakeholders` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/actions/polish
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/polish` 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 /{meeting_id}/actions/summarize
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/actions/summarize` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/chat
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/chat` 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 /{meeting_id}/check-feishu-url
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/check-feishu-url` 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 /{meeting_id}/create-action-kanban
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/create-action-kanban` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/export-feishu
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/export-feishu` 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 /{meeting_id}/process
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/process` 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 /{meeting_id}/requirements
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/requirements` 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 /{meeting_id}/stakeholders/rename
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/stakeholders/rename` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/sync-action-items
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/sync-action-items` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/sync-kb
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/sync-kb` 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 /{meeting_id}/sync-requirements
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/sync-requirements` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{meeting_id}/sync-stakeholder-map-kb
`meeting/backend/api/meeting.py` declares `POST /{meeting_id}/sync-stakeholder-map-kb` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{template_id}/activate
`meeting/backend/api/template.py` declares `POST /{template_id}/activate` 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 /{template_id}/export-docx
`meeting/backend/api/markup_template.py` declares `POST /{template_id}/export-docx` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{template_id}/export-md
`meeting/backend/api/markup_template.py` declares `POST /{template_id}/export-md` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{template_id}/render
`meeting/backend/api/markup_template.py` declares `POST /{template_id}/render` 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: PUT /credentials
`meeting/backend/api/feishu_credentials.py` declares `PUT /credentials` 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: PUT /feishu-credentials
`meeting/backend/api/meeting.py` declares `PUT /feishu-credentials` 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: PUT /{meeting_id}/edited-minutes
`meeting/backend/api/meeting.py` declares `PUT /{meeting_id}/edited-minutes` 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: PUT /{meeting_id}/process-flows
`meeting/backend/api/meeting.py` declares `PUT /{meeting_id}/process-flows` 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: PUT /{meeting_id}/project
`meeting/backend/api/meeting.py` declares `PUT /{meeting_id}/project` 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: PUT /{meeting_id}/stakeholder-map
`meeting/backend/api/meeting.py` declares `PUT /{meeting_id}/stakeholder-map` 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: backend/api/meeting.py (1854 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/api/outputs.py (1425 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/agentic/executor.py (1095 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/agentic/runner.py (3787 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/output_service.py (1094 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/api/client.ts (2708 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/components/console/research/ResearchQuestionnaire.tsx (1846 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/components/console/research/ResearchWorkspace.tsx (1186 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/pages/console/ConsoleMeetingDetail.tsx (2990 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/pages/console/ConsoleProjectDetail.tsx (2020 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/pages/Demo.tsx (1222 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/pages/demo/InsightDemo.tsx (886 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/pages/DesignSystem.tsx (1785 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/pages/Help.tsx (904 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/redesign/console/CenterWorkspace.tsx (1209 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/redesign/console/ConsoleProjectDetail.tsx (2046 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/redesign/console/research/ResearchQuestionnaireDark.tsx (1722 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/redesign/console/research/ResearchWorkspace.tsx (1273 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: meeting/backend/api/meeting.py (1854 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: meeting/frontend/src/pages/console/ConsoleMeetingDetail.tsx (2990 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/0391a7dd-bc23-4b84-8026-e6a384c31474/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0391a7dd-bc23-4b84-8026-e6a384c31474/

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.