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.

squall321/MXWhitePaper

https://github.com/squall321/MXWhitePaper · scanned 2026-06-16 00:20 UTC (2 months, 2 weeks ago)

362 raw signals (0 security + 362 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
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 58.5/100 with 100.0% coverage. It contains 8887 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 362 findings — concentrated in quality (179), frontend (62), api (50). Risk profile is high: 2 critical, 21 high, 85 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 160 of 274 actionable findings. 362 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 System graph security Secrets conf 1.00 Possible secret in apps/web/src/pages/Diag.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/web/src/pages/Diag.tsx:169
critical System graph security Secrets conf 1.00 Possible secret in apps/web/src/pages/Login.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
apps/web/src/pages/Login.tsx:22
high System graph security auth conf 1.00 FastAPI PATCH `patch_block` without auth dependency — apps/api/app/routers/documents.py:782
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:782 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_custom_css` without auth dependency — apps/api/app/routers/documents.py:695
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:695 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_infobox` without auth dependency — apps/api/app/routers/documents.py:610
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:610 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_section` without auth dependency — apps/api/app/routers/documents.py:741
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:741 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_title` without auth dependency — apps/api/app/routers/documents.py:561
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:561 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_variables` without auth dependency — apps/api/app/routers/documents.py:653
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:653 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `<anonymous>` without auth dependency — apps/api/app/routers/exports.py:277
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/exports.py:277 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_document` without auth dependency — apps/api/app/routers/documents.py:355
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:355 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_share_link` without auth dependency — apps/api/app/routers/sharing.py:128
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/sharing.py:128 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `export_pptx` without auth dependency — apps/api/app/routers/exports.py:193
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/exports.py:193 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `forgot_password` without auth dependency — apps/api/app/routers/auth_flows.py:195
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/auth_flows.py:195 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_csv` without auth dependency — apps/api/app/routers/imports.py:754
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/imports.py:754 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `insert_block` without auth dependency — apps/api/app/routers/documents.py:822
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:822 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `move_block` without auth dependency — apps/api/app/routers/documents.py:897
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:897 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `portal_callback` without auth dependency — apps/api/app/routers/portal_sso.py:157
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/portal_sso.py:157 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh` without auth dependency — apps/api/app/routers/auth.py:293
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/auth.py:293 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reorder_sections` without auth dependency — apps/api/app/routers/documents.py:945
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:945 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_password` without auth dependency — apps/api/app/routers/auth_flows.py:235
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/auth_flows.py:235 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `roundtrip_docx_endpoint` without auth dependency — apps/api/app/routers/imports.py:395
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/imports.py:395 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_email` without auth dependency — apps/api/app/routers/auth_flows.py:172
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/auth_flows.py:172 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `replace_document` without auth dependency — apps/api/app/routers/documents.py:397
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/app/routers/documents.py:397 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/components/blocks/FlowBlock.tsx:141
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/components/Highlight.tsx:8
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/features/search/components/CommandPalette.tsx:872
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/features/sharing/QrShare.tsx:67
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/lib/qr.ts:36
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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — apps/web/src/pages/TwoFactorSetup.tsx:146
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 — apps/web/src/components/blocks/WidgetExportMenu.tsx:85
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 — apps/web/src/features/editor/connectionStore.ts:84
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 — apps/web/src/features/editor/paste/imageRehydrate.ts:79
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 — apps/web/src/features/search/hooks/useSearch.ts:32
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 Frontend route `/*` has no Link/navigate to it — apps/web/src/components/__tests__/AuthGuard.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/auth/reset` has no Link/navigate to it — apps/web/src/pages/__tests__/ResetPassword.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/auth/verify` has no Link/navigate to it — apps/web/src/pages/__tests__/EmailVerify.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/docs/*` has no Link/navigate to it — apps/web/src/pages/__tests__/Login.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/docs/:slug/variables` has no Link/navigate to it — apps/web/src/pages/__tests__/DocumentVariables.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/docs/:slug/versions/:from/diff/:to` has no Link/navigate to it — apps/web/src/pages/__tests__/VersionDiff.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/me/2fa` has no Link/navigate to it — apps/web/src/pages/__tests__/TwoFactorSetup.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/present/:slug/notes` has no Link/navigate to it — apps/web/src/features/presentation/__tests__/PresenterView.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/present/:slug` has no Link/navigate to it — apps/web/src/features/presentation/__tests__/Presentation.theme.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/series/:slug` has no Link/navigate to it — apps/web/src/pages/__tests__/SeriesDetail.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/share/:token` has no Link/navigate to it — apps/web/src/pages/__tests__/SharedDocView.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/views/:id` has no Link/navigate to it — apps/web/src/pages/__tests__/SavedView.test.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.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 46 occurrences Frontend route `docs/new` has no Link/navigate to it — apps/web/src/main.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.
46 occurrences
repo-level (46 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/llm-docx-toolkit.yml:279
.github/workflows/zap.yml:35
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 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.
.github/workflows/llm-docx-toolkit.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/src/components/blocks/FlowBlock.tsx:141
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/src/components/blocks/FlowBlock.tsx:141 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/src/features/search/components/CommandPalette.tsx:872
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/src/features/search/components/CommandPalette.tsx:872 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/src/features/sharing/QrShare.tsx:67
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/src/features/sharing/QrShare.tsx:67 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in apps/web/src/pages/TwoFactorSetup.tsx:146
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
apps/web/src/pages/TwoFactorSetup.tsx:146 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/web/src/features/editor/components/InlineTextBlockEditor.tsx:103
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/web/src/features/editor/components/InlineTextBlockEditor.tsx:103 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in apps/web/src/main.tsx:298
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
apps/web/src/main.tsx:298 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/05-ideal-graph/dynamicgraph.html:519
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/05-ideal-graph/dynamicgraph.html:519 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in apps/api/app/services/totp.py:142
Found a known-risky pattern (weak_hash). Review and replace if possible.
apps/api/app/services/totp.py:142 Weak hash
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — examples/namu-archive-bulk/post-link.py:219
`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 405 placeholder/mock markers across 151 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 252 in use
Port 252 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/bootstrap-host.sh Ports
medium System graph network Security conf 1.00 Privileged port 6 in use
Port 6 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/restore-drill.yml Ports
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — apps/web/src/components/layout/TopBar.tsx:395
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 — apps/web/src/pages/CrossDocCompare.tsx:168
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 — apps/web/src/pages/VersionDiff.tsx:252
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 21 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AIDH_DEAD_LETTER_DIR`, `BASE_URL`, `BOOTSTRAP_ADMIN_EMAIL`, `BOOTSTRAP_ADMIN_NAME`, `BOOTSTRAP_ADMIN_PASSWORD`, `CI`, `DEV`, `MODE` + 13 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 169 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 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-artifact@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
4 files, 8 locations
.github/workflows/llm-docx-toolkit.yml:51, 112, 185, 271 (4 hits)
.github/workflows/e2e.yml:120, 129 (2 hits)
.github/workflows/apptainer-build.yml:40
.github/workflows/restore-drill.yml:178
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: apps/api/app/middleware/security.py:dispatch, apps/api/app/middleware/security.py:dispatch 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 separate.
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: apps/api/app/routers/retention.py:get_policy, apps/api/app/routers/retention.py:dry_run_policy, apps/api/app/routers/retention.py:run_policy_now This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: apps/api/app/scripts/seed_more_facts.py:main, apps/api/app/scripts/seed_widget_facts.py:main, apps/api/app/scripts/seed_form_quiz_defs.py:main, apps/api/app/scripts/seed_glossary.py:main This is *the* AI-coder failure mode (4× more duplication in vib…
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: apps/web/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
apps/web/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/shared/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/shared/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `allow_backup` in apps/api/tests/test_totp.py:394
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 `code_or_backup` in apps/api/app/routers/two_factor.py:17
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 `list_objects_v2` in apps/api/app/routers/health_dashboard.py:120
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 `list_objects_v2` in apps/api/app/services/upload_service.py:369
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 `list_objects_v2` in apps/api/tests/test_uploads.py:63
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 `pydantic_v2` in packages/shared/codegen/generate-py.py:51
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 `r_login_old` in apps/api/tests/test_auth_flows.py:327
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 `run_backup` in apps/api/app/routers/backups.py:35
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 `run_backup` in apps/api/app/services/backup_runner.py:148
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 `run_backup` in apps/api/tests/test_backups.py:1
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 `skipped_old` in integrations/aidatahub/aidatahub_sync.py:329
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 `test_select_versions_keeps_head_and_v1` in apps/api/tests/test_maintenance.py:60
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 `token_old` in apps/api/tests/test_api_tokens.py:182
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: build_discovery_link
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/routers/oembed.py:383
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/alembic/env.py:34
low System graph software Dead code conf 1.00 10 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
10 files, 10 locations
apps/api/alembic/versions/0010_snippets.py:50
apps/api/alembic/versions/0016_anchor_samples.py:53
apps/api/alembic/versions/0019_notification_prefs.py:28
apps/api/alembic/versions/0021_reactions.py:73
apps/api/alembic/versions/0023_api_tokens.py:51
apps/api/alembic/versions/0026_auth_tokens.py:48
apps/api/alembic/versions/0033_version_tags.py:68
apps/api/alembic/versions/0037_cron_timezone.py:42
low System graph software Dead code conf 1.00 Possibly dead Python function: emit_hidden_marker_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/services/widget_markers.py:136
low System graph software Dead code conf 1.00 Possibly dead Python function: list_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/repos/glossary_repo.py:387
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.
apps/api/app/services/variables.py:39
low System graph software Dead code conf 1.00 Possibly dead Python function: roundtrip_docx
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
apps/api/app/services/docx_roundtrip.py:26
low System graph software Dead code conf 1.00 10 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
10 files, 10 locations
apps/api/alembic/versions/0010_snippets.py:31
apps/api/alembic/versions/0016_anchor_samples.py:32
apps/api/alembic/versions/0019_notification_prefs.py:21
apps/api/alembic/versions/0021_reactions.py:25
apps/api/alembic/versions/0023_api_tokens.py:31
apps/api/alembic/versions/0026_auth_tokens.py:23
apps/api/alembic/versions/0033_version_tags.py:46
apps/api/alembic/versions/0037_cron_timezone.py:35
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 — apps/web/tests/e2e/_debug-search.spec.ts:10
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `_noop` (body is just `pass`/`return`) — apps/api/app/services/pptx_import.py:362
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /admin/retention-policies/{policy_id}
`apps/api/app/routers/retention.py` declares `DELETE /admin/retention-policies/{policy_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /glossary/proposals/{term_id}
`apps/api/app/routers/glossary.py` declares `DELETE /glossary/proposals/{term_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`apps/api/app/routers/notifications.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 /admin/audit-retention
`apps/api/app/routers/audit_retention.py` declares `GET /admin/audit-retention` 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 /admin/health-dashboard
`apps/api/app/routers/health_dashboard.py` declares `GET /admin/health-dashboard` 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: GET /admin/retention-policies
`apps/api/app/routers/retention.py` declares `GET /admin/retention-policies` 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 /admin/retention-policies/{policy_id}
`apps/api/app/routers/retention.py` declares `GET /admin/retention-policies/{policy_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/retention-policies/{policy_id}/runs
`apps/api/app/routers/retention.py` declares `GET /admin/retention-policies/{policy_id}/runs` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/healthz
`apps/api/app/main.py` declares `GET /api/v1/healthz` 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 /chart/audit-volume
`apps/api/app/routers/widgets.py` declares `GET /chart/audit-volume` 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 /chart/cohort-retention
`apps/api/app/routers/widgets.py` declares `GET /chart/cohort-retention` 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 /chart/funnel-conversion
`apps/api/app/routers/widgets.py` declares `GET /chart/funnel-conversion` 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 /chart/month-end-progress
`apps/api/app/routers/widgets.py` declares `GET /chart/month-end-progress` 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 /chart/region-share
`apps/api/app/routers/widgets.py` declares `GET /chart/region-share` 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 /chart/sales-trend
`apps/api/app/routers/widgets.py` declares `GET /chart/sales-trend` 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 /chart/team-share
`apps/api/app/routers/widgets.py` declares `GET /chart/team-share` 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 /definitions
`apps/api/app/routers/quiz.py` declares `GET /definitions` 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 /definitions/{quiz_id:path}
`apps/api/app/routers/quiz.py` declares `GET /definitions/{quiz_id:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /glossary
`apps/api/app/routers/glossary.py` declares `GET /glossary` 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 /glossary/pending
`apps/api/app/routers/glossary.py` declares `GET /glossary/pending` 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 /glossary/term/{term}
`apps/api/app/routers/glossary.py` declares `GET /glossary/term/{term}` 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 /kpi-finance-daily-summary
`apps/api/app/routers/widgets.py` declares `GET /kpi-finance-daily-summary` 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 /kpi/{key:path}
`apps/api/app/routers/widgets.py` declares `GET /kpi/{key:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /launch/{program}/forecast
`apps/api/app/routers/widgets.py` declares `GET /launch/{program}/forecast` 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 /launch/{program}/tasks
`apps/api/app/routers/widgets.py` declares `GET /launch/{program}/tasks` 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 /launch/{program}/timeline
`apps/api/app/routers/widgets.py` declares `GET /launch/{program}/timeline` 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 /me/{slug}/{block_id}
`apps/api/app/routers/quiz.py` declares `GET /me/{slug}/{block_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 /registry
`apps/api/app/routers/widgets.py` declares `GET /registry` 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 /table/campaigns-active
`apps/api/app/routers/widgets.py` declares `GET /table/campaigns-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 /table/documents-top
`apps/api/app/routers/widgets.py` declares `GET /table/documents-top` 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 /table/glossary-top
`apps/api/app/routers/widgets.py` declares `GET /table/glossary-top` 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 /table/incidents-recent
`apps/api/app/routers/widgets.py` declares `GET /table/incidents-recent` 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 /table/region-breakdown
`apps/api/app/routers/widgets.py` declares `GET /table/region-breakdown` 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 /table/sales-summary
`apps/api/app/routers/widgets.py` declares `GET /table/sales-summary` 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 /{kind}/{widget_id:path}
`apps/api/app/routers/widgets.py` declares `GET /{kind}/{widget_id:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{slug}/{block_id}/attempts
`apps/api/app/routers/quiz.py` declares `GET /{slug}/{block_id}/attempts` 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 /{slug}/{block_id}/leaderboard
`apps/api/app/routers/quiz.py` declares `GET /{slug}/{block_id}/leaderboard` 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 /admin/audit-retention
`apps/api/app/routers/audit_retention.py` declares `PATCH /admin/audit-retention` 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: PATCH /admin/retention-policies/{policy_id}
`apps/api/app/routers/retention.py` declares `PATCH /admin/retention-policies/{policy_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /glossary/proposals/{term_id}
`apps/api/app/routers/glossary.py` declares `PATCH /glossary/proposals/{term_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /glossary/{term_id}
`apps/api/app/routers/glossary.py` declares `PATCH /glossary/{term_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 /admin/audit-retention/prune-now
`apps/api/app/routers/audit_retention.py` declares `POST /admin/audit-retention/prune-now` 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 /admin/retention-policies
`apps/api/app/routers/retention.py` declares `POST /admin/retention-policies` 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 /admin/retention-policies/{policy_id}/dry-run
`apps/api/app/routers/retention.py` declares `POST /admin/retention-policies/{policy_id}/dry-run` 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 documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/retention-policies/{policy_id}/run
`apps/api/app/routers/retention.py` declares `POST /admin/retention-policies/{policy_id}/run` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /glossary/propose
`apps/api/app/routers/glossary.py` declares `POST /glossary/propose` 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 /glossary/{term_id}/approve
`apps/api/app/routers/glossary.py` declares `POST /glossary/{term_id}/approve` 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 /glossary/{term_id}/reject
`apps/api/app/routers/glossary.py` declares `POST /glossary/{term_id}/reject` 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 /{nid}/read
`apps/api/app/routers/notifications.py` declares `POST /{nid}/read` 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 /{slug}/{block_id}/attempts
`apps/api/app/routers/quiz.py` declares `POST /{slug}/{block_id}/attempts` 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: apps/api/app/schemas/document.py (2738 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/document_service.py (2034 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/docx_export.py (1795 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/docx_import.py (2303 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/html_renderer.py (1402 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/pptx_export.py (1635 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/api/app/services/widget_markers.py (1991 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web/src/features/editor/blocks/ChartBlockEditor.tsx (2065 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web/src/features/graph/components/KnowledgeGraph.tsx (1344 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: apps/web/src/lib/i18n/ko.ts (1084 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/bc648682-f10b-4eca-95b8-ca112b74a320/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bc648682-f10b-4eca-95b8-ca112b74a320/

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.