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

senai-data/sen-ai-website

https://github.com/senai-data/sen-ai-website · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

165 raw signals (0 security + 165 graph)

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

Complete repo analysis

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

JSON
Combined
70.0
/100
Security checks
70
0 findings
System graph
70
100.0% cov · 157 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 7 Medium 17 Low 82 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 157 Crowd 0 Layer: Software 8 Hardware 5 Frontend 1 Security 17 Cicd 1 Quality 75 Api 50
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 70.0/100 with 100.0% coverage. It contains 2054 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 165 findings — concentrated in quality (83), api (50), security (17). Risk profile is high: 0 critical, 7 high, 17 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high System graph security auth conf 1.00 FastAPI POST `confirm_audit_request` without auth dependency — api/routers/audit_requests.py:220
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/audit_requests.py:220 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_audit_request` without auth dependency — api/routers/audit_requests.py:146
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/audit_requests.py:146 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `forgot_password` without auth dependency — api/routers/auth.py:539
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/auth.py:539 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset_password` without auth dependency — api/routers/auth.py:552
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/auth.py:552 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stripe_webhook` without auth dependency — api/routers/stripe.py:179
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/stripe.py:179 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `verify_email` without auth dependency — api/routers/auth.py:152
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/auth.py:152 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in scripts/smoke_j1_j3.sh:125
Found a known-risky pattern (eval_used). Review and replace if possible.
scripts/smoke_j1_j3.sh:125 Eval used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/scan-header.ts:96
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 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: api/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: worker/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/01-tokens.html:385
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/01-tokens.html:385 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/02-components.html:336
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/02-components.html:336 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/03-flagship.html:389
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/03-flagship.html:389 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/04-navigation.html:260
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/04-navigation.html:260 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/06-citations.html:475
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/06-citations.html:475 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/07-create-scan.html:271
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/07-create-scan.html:271 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/08-compliance.html:346
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/08-compliance.html:346 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/09-content.html:249
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/09-content.html:249 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/10-dashboard.html:249
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/10-dashboard.html:249 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design-handoff/11-branding.html:252
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design-handoff/11-branding.html:252 Direct innerhtml assignment
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 15 placeholder/mock markers across 10 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
9 test file(s) for 181 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. 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 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 649 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: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
api/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
worker/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 11 places
Functions with the same first-5-line body hash: worker/scripts/restore_furterer_brief.py:main, worker/scripts/fix_klorane_brief.py:main, worker/scripts/import_seollm_klorane.py:main, worker/scripts/import_seollm_ducray.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded …
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: api/models.py:get_db, worker/models.py:get_db 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.
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: api/routers/scans.py:refresh_pr_outreach, api/routers/scans.py:refresh_internal_linking, api/routers/scans.py:refresh_youtube_creators This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: api/services/oauth_providers.py:authorize_url, api/services/oauth_providers.py:authorize_url, api/services/oauth_providers.py:authorize_url, api/services/oauth_providers.py:authorize_url This is *the* AI-coder failure mode (4× more duplication in vib…
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_months_old` in worker/services/media_catalog_io.py:170
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 `domain_brief_backup` in worker/scripts/regen_brief.py:23
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `len_old` in api/routers/content_items.py:810
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 `months_old` in api/models.py:1064
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 `rest_v1` in worker/adapters/wikipedia_client.py:319
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 `unpublish_old` in api/routers/reports.py:166
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: decorator
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker/main.py:104
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_credits
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker/adapters/haloscan_client.py:101
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_domain_top_pages
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker/adapters/haloscan_client.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: require_app
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/services/feature_gate.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: require_superadmin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/routers/reports.py:31
low System graph software Dead code conf 1.00 Possibly dead Python function: reset_user
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/services/agent_quota.py:76
low System graph software Dead code conf 1.00 Possibly dead Python function: summarize_warnings
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker/heuristics.py:279
low System graph software Dead code conf 1.00 Possibly dead Python function: test_question_openai_direct
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker/adapters/llm_scanner.py:179
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 quality Integrity conf 1.00 Stub function `_try_generate_image` (body is just `pass`/`return`) — worker/handlers/generate_article.py:121
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 /api/clients/active
`api/routers/clients.py` declares `DELETE /api/clients/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: DELETE /api/clients/{client_id}/brands/{brand_id}/pages/manual
`api/routers/clients.py` declares `DELETE /api/clients/{client_id}/brands/{brand_id}/pages/manual` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/organizations/active
`api/routers/organizations.py` declares `DELETE /api/organizations/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: DELETE /api/organizations/{org_id}/members/{user_id}
`api/routers/organizations.py` declares `DELETE /api/organizations/{org_id}/members/{user_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/organizations/{org_id}/members/{user_id}/clients/{client_id}
`api/routers/organizations.py` declares `DELETE /api/organizations/{org_id}/members/{user_id}/clients/{client_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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/admin/reports/
`api/routers/reports.py` declares `GET /api/admin/reports/` 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 /api/admin/reports/suggestions
`api/routers/reports.py` declares `GET /api/admin/reports/suggestions` 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 /api/clients/
`api/routers/clients.py` declares `GET /api/clients/` 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 /api/clients/{client_id}/brands/{brand_id}/brief
`api/routers/clients.py` declares `GET /api/clients/{client_id}/brands/{brand_id}/brief` 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 /api/clients/{client_id}/brands/{brand_id}/pages
`api/routers/clients.py` declares `GET /api/clients/{client_id}/brands/{brand_id}/pages` 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 /api/clients/{client_id}/brands/{brand_id}/sitemap-config
`api/routers/clients.py` declares `GET /api/clients/{client_id}/brands/{brand_id}/sitemap-config` 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: GET /api/clients/{client_id}/brief
`api/routers/clients.py` declares `GET /api/clients/{client_id}/brief` 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 /api/clients/{client_id}/promotion
`api/routers/clients.py` declares `GET /api/clients/{client_id}/promotion` 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 /api/clients/{client_id}/trust-sources
`api/routers/clients.py` declares `GET /api/clients/{client_id}/trust-sources` 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 /api/health
`api/main.py` declares `GET /api/health` 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 /api/methodology/pdf
`api/main.py` declares `GET /api/methodology/pdf` 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 /api/organizations/
`api/routers/organizations.py` declares `GET /api/organizations/` 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 /api/organizations/{org_id}
`api/routers/organizations.py` declares `GET /api/organizations/{org_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 /api/organizations/{org_id}/compliance/pdf
`api/routers/organizations.py` declares `GET /api/organizations/{org_id}/compliance/pdf` 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 /api/organizations/{org_id}/overview
`api/routers/organizations.py` declares `GET /api/organizations/{org_id}/overview` 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 /api/organizations/{org_id}/workspaces/overview
`api/routers/organizations.py` declares `GET /api/organizations/{org_id}/workspaces/overview` 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/stripe/credits/{client_id}
`api/routers/stripe.py` declares `GET /api/stripe/credits/{client_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 /api/stripe/credits/{client_id}/history
`api/routers/stripe.py` declares `GET /api/stripe/credits/{client_id}/history` 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 /api/stripe/packs
`api/routers/stripe.py` declares `GET /api/stripe/packs` 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 /api/clients/{client_id}
`api/routers/clients.py` declares `PATCH /api/clients/{client_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 /api/clients/{client_id}/brands/{brand_id}/brief
`api/routers/clients.py` declares `PATCH /api/clients/{client_id}/brands/{brand_id}/brief` 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 /api/clients/{client_id}/brands/{brand_id}/parent
`api/routers/clients.py` declares `PATCH /api/clients/{client_id}/brands/{brand_id}/parent` 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 /api/organizations/{org_id}
`api/routers/organizations.py` declares `PATCH /api/organizations/{org_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 /api/organizations/{org_id}/branding
`api/routers/organizations.py` declares `PATCH /api/organizations/{org_id}/branding` 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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/organizations/{org_id}/members/{user_id}
`api/routers/organizations.py` declares `PATCH /api/organizations/{org_id}/members/{user_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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /
`api/routers/audit_requests.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 /api/admin/reports/
`api/routers/reports.py` declares `POST /api/admin/reports/` 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 /api/admin/reports/{report_id}/unpublish
`api/routers/reports.py` declares `POST /api/admin/reports/{report_id}/unpublish` 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 /api/clients/
`api/routers/clients.py` declares `POST /api/clients/` 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 /api/clients/active
`api/routers/clients.py` declares `POST /api/clients/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: POST /api/clients/{client_id}/brands/{brand_id}/brief/generate
`api/routers/clients.py` declares `POST /api/clients/{client_id}/brands/{brand_id}/brief/generate` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/clients/{client_id}/brands/{brand_id}/pages/manual
`api/routers/clients.py` declares `POST /api/clients/{client_id}/brands/{brand_id}/pages/manual` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/clients/{client_id}/brands/{brand_id}/sitemap/refresh
`api/routers/clients.py` declares `POST /api/clients/{client_id}/brands/{brand_id}/sitemap/refresh` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/clients/{client_id}/brief/generate
`api/routers/clients.py` declares `POST /api/clients/{client_id}/brief/generate` 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 /api/clients/{client_id}/trust-sources/discover
`api/routers/clients.py` declares `POST /api/clients/{client_id}/trust-sources/discover` 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: POST /api/clients/{client_id}/trust-sources/extra-domains
`api/routers/clients.py` declares `POST /api/clients/{client_id}/trust-sources/extra-domains` 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 /api/organizations/active
`api/routers/organizations.py` declares `POST /api/organizations/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: POST /api/organizations/{org_id}/clients
`api/routers/organizations.py` declares `POST /api/organizations/{org_id}/clients` 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 /api/organizations/{org_id}/clients/bulk
`api/routers/organizations.py` declares `POST /api/organizations/{org_id}/clients/bulk` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/stripe/checkout
`api/routers/stripe.py` declares `POST /api/stripe/checkout` 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 /api/stripe/webhook
`api/routers/stripe.py` declares `POST /api/stripe/webhook` 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 /confirm
`api/routers/audit_requests.py` declares `POST /confirm` 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 /api/clients/{client_id}/brief
`api/routers/clients.py` declares `PUT /api/clients/{client_id}/brief` 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 /api/clients/{client_id}/promotion
`api/routers/clients.py` declares `PUT /api/clients/{client_id}/promotion` 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 /api/organizations/{org_id}/members/{user_id}/clients/{client_id}
`api/routers/organizations.py` declares `PUT /api/organizations/{org_id}/members/{user_id}/clients/{client_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 removin…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: api/models.py (1128 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/routers/clients.py (1500 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/routers/content_items.py (1717 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: api/routers/scans.py (5560 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/handlers/generate_article.py (1806 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: worker/services/media_replacement.py (1194 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/4a832cf8-6067-4c1c-be37-c5bad2d46574/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4a832cf8-6067-4c1c-be37-c5bad2d46574/

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.