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

Alexis-beep-debug/email-outreach-dynvon

https://github.com/Alexis-beep-debug/email-outreach-dynvon · scanned 2026-06-17 01:16 UTC (1 month, 2 weeks ago)

213 raw signals (0 security + 213 graph)

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

Complete repo analysis

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

JSON
Combined
47.4
/100
Security checks
47
0 findings
System graph
47
88.9% cov · 189 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 32 Medium 38 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 189 Crowd 0 Layer: Software 21 Frontend 42 Network 2 Hardware 3 Security 35 Quality 27 Api 59
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 47.4/100 with 88.9% coverage. It contains 2632 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 213 findings — concentrated in api (59), quality (51), frontend (42). Risk profile is high: 0 critical, 32 high, 48 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/campaigns/${id}/steps/${stepId} (dashboard/src/pages/CampaignDetail.jsx:52)
`dashboard/src/pages/CampaignDetail.jsx:52` calls `DELETE /api/campaigns/${id}/steps/${stepId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/campaigns/<p>/steps/<p>` If this points at an external API, prefix it wi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/analytics${path} (dashboard/src/pages/WebAnalytics.jsx:12)
`dashboard/src/pages/WebAnalytics.jsx:12` calls `GET /api/analytics${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/analytics/<p>` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/check (dashboard/src/App.jsx:182)
`dashboard/src/App.jsx:182` calls `GET /api/auth/check` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/check` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/auth/invite-info?token=${token} (dashboard/src/pages/Register.jsx:22)
`dashboard/src/pages/Register.jsx:22` calls `GET /api/auth/invite-info?token=${token}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/invite-info` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/campaigns/${id}/steps/${editingStep.stepId} (dashboard/src/pages/CampaignDetail.jsx:35)
`dashboard/src/pages/CampaignDetail.jsx:35` calls `PATCH /api/campaigns/${id}/steps/${editingStep.stepId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/campaigns/<p>/steps/<p>` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/campaigns/${id}/variants/${editingVariant.variantId} (dashboard/src/pages/CampaignDetail.jsx:66)
`dashboard/src/pages/CampaignDetail.jsx:66` calls `PATCH /api/campaigns/${id}/variants/${editingVariant.variantId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/campaigns/<p>/variants/<p>` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/login (dashboard/src/pages/Login.jsx:18)
`dashboard/src/pages/Login.jsx:18` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/logout (dashboard/src/App.jsx:221)
`dashboard/src/App.jsx:221` calls `POST /api/auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/auth/register (dashboard/src/pages/Register.jsx:73)
`dashboard/src/pages/Register.jsx:73` calls `POST /api/auth/register` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/register` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_job` without auth dependency — app/api/scraper.py:553
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:553 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `complete_job` without auth dependency — app/api/scraper.py:326
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:326 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `confirm_unsubscribe` without auth dependency — app/api/tracking.py:106
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/tracking.py:106 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `enrich_leads_csv` without auth dependency — app/api/leads.py:441
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/leads.py:441 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fail_job` without auth dependency — app/api/scraper.py:344
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:344 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_from_close` without auth dependency — app/api/close_crm.py:37
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/close_crm.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_leads_from_job` without auth dependency — app/api/scraper.py:398
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:398 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `migrate_columns` without auth dependency — app/api/crm_setup.py:329
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/crm_setup.py:329 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `personalize_leads` without auth dependency — app/api/scraper.py:510
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:510 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preview_crm_leads_csv` without auth dependency — app/api/crm/leads_unified.py:487
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/crm/leads_unified.py:487 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preview_csv` without auth dependency — app/api/leads.py:65
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/leads.py:65 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `push_call_priority` without auth dependency — app/api/close_crm.py:136
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/close_crm.py:136 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `push_to_close` without auth dependency — app/api/close_crm.py:55
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/close_crm.py:55 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `replay_dlq_entry` without auth dependency — app/api/ops.py:53
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/ops.py:53 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_scraping` without auth dependency — app/api/scraper.py:56
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:56 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sync_activities` without auth dependency — app/api/close_crm.py:72
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/close_crm.py:72 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_click` without auth dependency — app/api/analytics.py:120
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/analytics.py:120 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_pageview` without auth dependency — app/api/analytics.py:88
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/analytics.py:88 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `track_scroll` without auth dependency — app/api/analytics.py:147
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/analytics.py:147 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_job_progress` without auth dependency — app/api/scraper.py:307
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:307 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_results` without auth dependency — app/api/scraper.py:370
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:370 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_scraped_leads` without auth dependency — app/api/scraper.py:361
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
app/api/scraper.py:361 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in agents/website_fetcher.py:55
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
agents/website_fetcher.py:55 Tls verify false
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — dashboard/src/components/EmailComposer.jsx:230
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 — dashboard/src/components/EmailsSection.jsx:140
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 — dashboard/src/components/EmailThread.jsx:54
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 — dashboard/src/pages/Aufgaben.jsx:282
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 — dashboard/src/pages/CampaignCreate.jsx:368
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 — dashboard/src/pages/CampaignDetail.jsx:176
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 — dashboard/src/pages/CRMInbox.jsx:444
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 — dashboard/src/pages/CRMSettings.jsx:610
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 — dashboard/src/pages/DealDetail.jsx:1526
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 — dashboard/src/pages/KontaktDetail.jsx:1097
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 — dashboard/src/pages/OrganisationDetail.jsx:395
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 — dashboard/src/pages/SentEmails.jsx:104
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 — dashboard/src/App.jsx:182
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 — dashboard/src/components/DashboardPage.jsx:213
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 — dashboard/src/pages/CloseCRM.jsx:7
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 — dashboard/src/pages/WebAnalytics.jsx:12
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 — dashboard/src/utils/api.js:147
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, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 11 occurrences Frontend route `/kunden/:id` has no Link/navigate to it — dashboard/src/App.jsx
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.
11 occurrences
repo-level (11 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/components/EmailComposer.jsx:230
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/components/EmailComposer.jsx:230 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/components/EmailsSection.jsx:140
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/components/EmailsSection.jsx:140 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/components/EmailThread.jsx:54
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/components/EmailThread.jsx:54 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/Aufgaben.jsx:282
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/Aufgaben.jsx:282 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/CampaignCreate.jsx:368
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/CampaignCreate.jsx:368 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/CampaignDetail.jsx:176
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/CampaignDetail.jsx:176 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/CRMInbox.jsx:444
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/CRMInbox.jsx:444 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/CRMSettings.jsx:610
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/CRMSettings.jsx:610 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/DealDetail.jsx:1526
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/DealDetail.jsx:1526 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/KontaktDetail.jsx:1097
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/KontaktDetail.jsx:1097 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/OrganisationDetail.jsx:395
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/OrganisationDetail.jsx:395 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in dashboard/src/pages/SentEmails.jsx:104
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
dashboard/src/pages/SentEmails.jsx:104 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/branche_backfill.py:51
`urllib.request.urlopen(...)` 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 151 placeholder/mock markers across 30 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 465 in use
Port 465 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
app/api/replies.py Ports
medium System graph network Security conf 1.00 Privileged port 993 in use
Port 993 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
app/services/imap_service.py Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
22 test file(s) for 271 source file(s) (ratio 0.08). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 18 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `DASHBOARD_URL`, `DRY`, `EXT_PREFIX`, `GOOGLE_API_KEY`, `GOOGLE_CSE_ID`, `GOOGLE_MAPS_API_KEY`, `GOOGLE_SERVICE_ACCOUNT_JSON`, `MILLIONVERIFIER_API_KEY` + 10 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, 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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 666 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: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
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.
Dockerfile:10 containersPinned dependencies
low System graph quality Integrity conf 1.00 13 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: app/main.py:serve_dashboard_root, app/main.py:serve_dashboard 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.
13 occurrences
repo-level (13 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: app/api/projects.py:get_projects_by_customer, app/api/projects.py:get_projects, app/api/projects.py:get_project This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `cache_sample_1000_v2` in run_score_1000_v2.py:15
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 `lead_pipeline_v2` in agents/lead_pipeline_v2.py:14
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 `lead_pipeline_v2` in app/api/scraper.py:127
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: add_request_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/infrastructure/logging_config.py:18
low System graph software Dead code conf 1.00 Possibly dead Python function: check_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/duplicate_detector.py:239
low System graph software Dead code conf 1.00 Possibly dead Python function: create_contact
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:81
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.
app/infrastructure/retry_config.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: enrich_leads_csv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/lead_enrichment.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: initiate_call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/placetel.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: progress
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
local_scraper.py:216
low System graph software Dead code conf 1.00 Possibly dead Python function: progress
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
lead_scraper/cli.py:90
low System graph software Dead code conf 1.00 Possibly dead Python function: progress_cb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
worker.py:191
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_link
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/tracking/tracker.py:51
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_var
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/template_engine.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: require_admin
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/auth_utils.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: search_by_address
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/imap_service.py:158
low System graph software Dead code conf 1.00 Possibly dead Python function: search_contacts_by_email
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:143
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_bounce_to_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:399
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_click_to_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:382
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_meeting_to_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:413
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_open_to_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:365
low System graph software Dead code conf 1.00 Possibly dead Python function: sync_reply_to_close
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:350
low System graph software Dead code conf 1.00 Possibly dead Python function: update_lead_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/services/close_crm.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_email_smtp
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
lead_scraper/extractors/email_finder.py:41
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — dashboard/src/hooks/useWebexCalling.js:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /
`app/api/leads.py` declares `DELETE /` 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 /disconnect
`app/api/webex.py` declares `DELETE /disconnect` 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 /{lead_id}
`app/api/leads.py` declares `DELETE /{lead_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{project_id}
`app/api/projects.py` declares `DELETE /{project_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{task_id}
`app/api/tasks.py` declares `DELETE /{task_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 /
`app/main.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 /ab-tests
`app/api/dashboard.py` declares `GET /ab-tests` 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 /analytics/script.js
`app/api/tracking_script.py` declares `GET /analytics/script.js` 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/analytics/overview
`app/api/analytics.py` declares `GET /api/analytics/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/analytics/scroll-dropoff
`app/api/analytics.py` declares `GET /api/analytics/scroll-dropoff` 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/analytics/timeline
`app/api/analytics.py` declares `GET /api/analytics/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 /authorize
`app/api/webex.py` declares `GET /authorize` 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 /by-customer
`app/api/projects.py` declares `GET /by-customer` 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 /callback
`app/api/webex.py` declares `GET /callback` 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 /campaign-comparison
`app/api/dashboard.py` declares `GET /campaign-comparison` 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 /dashboard
`app/main.py` declares `GET /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/
`app/main.py` declares `GET /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /dashboard/{path:path}
`app/main.py` declares `GET /dashboard/{path: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 /dynvon-kmu-outreach
`app/api/templates.py` declares `GET /dynvon-kmu-outreach` 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 /overview
`app/api/dashboard.py` declares `GET /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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sending-accounts
`app/api/dashboard.py` declares `GET /sending-accounts` 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 /sent
`app/api/sent_emails.py` declares `GET /sent` 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 /sent/campaigns
`app/api/sent_emails.py` declares `GET /sent/campaigns` 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 /sent/{lead_id}/timeline
`app/api/sent_emails.py` declares `GET /sent/{lead_id}/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 /summary
`app/api/costs.py` declares `GET /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 /timeline
`app/api/dashboard.py` declares `GET /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 /token
`app/api/webex.py` declares `GET /token` 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 /track/click/{tracking_id}
`app/api/tracking.py` declares `GET /track/click/{tracking_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 /track/open/{tracking_id}.png
`app/api/tracking.py` declares `GET /track/open/{tracking_id}.png` 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 /unsubscribe/{token}
`app/api/tracking.py` declares `GET /unsubscribe/{token}` 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 /{lead_id}
`app/api/leads.py` declares `GET /{lead_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 /{lead_id}/emails
`app/api/leads.py` declares `GET /{lead_id}/emails` 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 /{project_id}
`app/api/projects.py` declares `GET /{project_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 /{task_id}
`app/api/tasks.py` declares `PATCH /{task_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 /{task_id}/move
`app/api/tasks.py` declares `PATCH /{task_id}/move` 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 /
`app/api/tasks.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 /analytics/click
`app/api/analytics.py` declares `POST /analytics/click` 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 /analytics/pageview
`app/api/analytics.py` declares `POST /analytics/pageview` 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 /analytics/scroll
`app/api/analytics.py` declares `POST /analytics/scroll` 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 /disconnect
`app/api/webex.py` declares `POST /disconnect` 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 /dynvon-kmu-outreach/create
`app/api/templates.py` declares `POST /dynvon-kmu-outreach/create` 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 /enrich
`app/api/leads.py` declares `POST /enrich` 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 /import
`app/api/leads.py` declares `POST /import` 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 /import-mapped
`app/api/leads.py` declares `POST /import-mapped` 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 /migrate-columns
`app/api/crm_setup.py` declares `POST /migrate-columns` 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 /preview
`app/api/leads.py` declares `POST /preview` 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 /seed
`app/api/crm_setup.py` declares `POST /seed` 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 /unsubscribe/{token}/confirm
`app/api/tracking.py` declares `POST /unsubscribe/{token}/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 /{lead_id}/personalization
`app/api/leads.py` declares `PUT /{lead_id}/personalization` 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 /{project_id}
`app/api/projects.py` declares `PUT /{project_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 quality Complexity conf 1.00 Very large file: app/api/test_email.py (2127 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dashboard/src/pages/CRMSettings.jsx (2062 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dashboard/src/pages/DealDetail.jsx (1983 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dashboard/src/pages/KontaktDetail.jsx (1935 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: dashboard/src/pages/LeadsUnified.jsx (1282 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/0576c940-fc46-484c-8d99-e0f529068931/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0576c940-fc46-484c-8d99-e0f529068931/

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.