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

Zakariakhchiche/DEMOEMA

https://github.com/Zakariakhchiche/DEMOEMA · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

187 raw signals (0 security + 187 graph)

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

Complete repo analysis

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

JSON
Combined
38.4
/100
Security checks
38
0 findings
System graph
38
100.0% cov · 166 findings
Critical
1
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 1 High 13 Medium 19 Low 101 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 166 Crowd 0 Layer: Software 28 Frontend 13 Network 4 Hardware 7 Security 6 Cicd 2 Quality 48 Api 58
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 38.4/100 with 100.0% coverage. It contains 2616 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 187 findings — concentrated in api (58), quality (50), software (28). Risk profile is high: 1 critical, 13 high, 21 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

critical System graph security Secrets conf 1.00 Possible secret in .gitleaks.toml
Detected pattern matching openai_or_anthropic_key. Rotate the credential and move to a secret manager.
.gitleaks.toml:64
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/datalake/dashboard (frontend/src/components/dem/TopHeader.tsx:44)
`frontend/src/components/dem/TopHeader.tsx:44` calls `GET /api/datalake/dashboard` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/datalake/dashboard` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/datalake/entreprise/search?q=${encodeURIComponent(q)}&limit=${limit} (frontend/src/lib/dem/adapter.ts:277)
`frontend/src/lib/dem/adapter.ts:277` calls `GET /api/datalake/entreprise/search?q=${encodeURIComponent(q)}&limit=${limit}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/datalake/entreprise/search` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/datalake/fiche/${siren} (frontend/src/components/dem/CompareView.tsx:173)
`frontend/src/components/dem/CompareView.tsx:173` calls `GET /api/datalake/fiche/${siren}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/datalake/fiche/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/datalake/graph (frontend/src/lib/queries/useGraph.ts:48)
`frontend/src/lib/queries/useGraph.ts:48` calls `GET /api/datalake/graph` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/datalake/graph` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/scoring/config (frontend/src/app/targets/page.tsx:104)
`frontend/src/app/targets/page.tsx:104` calls `GET /api/scoring/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scoring/config` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/datalake/agent-retry/${a.source_id} (frontend/src/components/dem/AuditView.tsx:159)
`frontend/src/components/dem/AuditView.tsx:159` calls `POST /api/datalake/agent-retry/${a.source_id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/datalake/agent-retry/<p>` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/pipeline/move (frontend/src/lib/queries/usePipeline.ts:42)
`frontend/src/lib/queries/usePipeline.ts:42` calls `POST /api/pipeline/move` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pipeline/move` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/scoring/config (frontend/src/app/targets/page.tsx:155)
`frontend/src/app/targets/page.tsx:155` calls `POST /api/scoring/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/scoring/config` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `copilot_redteam` without auth dependency — backend/main.py:1860
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/main.py:1860 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `move_pipeline_card` without auth dependency — backend/routers/pipeline.py:47
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/pipeline.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_targets` without auth dependency — backend/main.py:2670
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/main.py:2670 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_scoring_config` without auth dependency — backend/routers/scoring.py:23
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/scoring.py:23 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in backend/pyproject.toml:32
Found a known-risky pattern (eval_used). Review and replace if possible.
backend/pyproject.toml:32 Eval used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/public/sw.js:1
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/targets/[id]/page.tsx:60
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/CommandPalette.tsx:60
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/dem/TargetSheet.tsx:308
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/dem/TopHeader.tsx:44
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/queries/useGraph.ts:48
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/queries/usePipeline.ts:30
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/queries/useSignals.ts:31
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/queries/useTarget.ts:8
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/queries/useTargets.ts:8
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: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: infrastructure/agents/platform/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
webfactory/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 3 locations
.github/workflows/deploy-ionos.yml:34, 70 (2 hits)
.github/workflows/qa-security.yml:90
CI/CD securitySupply chainGithub actions
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 58 placeholder/mock markers across 26 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 143 in use
Port 143 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infrastructure/agents/signup/setup-postfix.sh Ports
medium System graph network Security conf 1.00 Privileged port 2 in use
Port 2 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infrastructure/scripts/bootstrap-vps.sh Ports
medium System graph network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
infrastructure/scripts/bootstrap-vps.sh Ports
medium System graph network Security conf 1.00 Privileged port 5 in use
Port 5 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/qa-security.yml Ports
low System graph quality Integrity conf 1.00 39 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENTS_PLATFORM_URL`, `BACKEND_INTERNAL_URL`, `BACKEND_URL`, `BUILD_TARGET`, `CI`, `CODEGEN_USE_TOOLS`, `CORS_ORIGIN_REGEX`, `CRON_SECRET` + 31 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 450 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: mcr.microsoft.com/playwright/python:v1.48.0-jammy
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
infrastructure/agents/signup/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 3 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 7, 15
frontend/Dockerfile:2, 7, 15 (3 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
infrastructure/agents/platform/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.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 16 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
5 files, 16 locations
.github/workflows/security-redteam.yml:41, 44, 154, 165 (4 hits)
.github/workflows/qa-data-quality.yml:34, 37, 67 (3 hits)
.github/workflows/qa-mutation-testing.yml:29, 32, 88 (3 hits)
.github/workflows/qa-qcs-tracker.yml:32, 169, 179 (3 hits)
.github/workflows/qa-security.yml:33, 36, 147 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
47 tests / 271 src (ratio 0.17).
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: infrastructure/agents/platform/main.py:stream, infrastructure/agents/platform/main.py:stream This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separa…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: infrastructure/agents/signup/signup_agent/flows/france_travail.py:run, infrastructure/agents/signup/signup_agent/flows/inpi_rne.py:run, infrastructure/agents/signup/signup_agent/flows/piste_gouv.py:run This is *the* AI-coder failure mode (4× more dup…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_scoring_detail_legacy` in backend/routers/datalake.py:2826
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 `recaptcha_v2` in infrastructure/agents/platform/tools/captcha.py:79
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: count_opendatasoft
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/counters.py:88
low System graph software Dead code conf 1.00 Possibly dead Python function: count_via_header
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/counters.py:93
low System graph software Dead code conf 1.00 Possibly dead Python function: embed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ollama_client.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_basol_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/basol.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_bdpm_medicaments_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/bdpm_medicaments.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_dvf_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/dvf.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_esane_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/esane.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_eurostat_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/eurostat.py:29
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_inpi_brevets_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/inpi_brevets.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_opensanctions_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/opensanctions.py:27
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_recherche_entreprises_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/recherche_entreprises.py:30
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_urssaf_opendata_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/sources/urssaf_opendata.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: list_gold_specs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/gold_codegen.py:115
low System graph software Dead code conf 1.00 Possibly dead Python function: list_silver_specs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/silver_codegen.py:915
low System graph software Dead code conf 1.00 Possibly dead Python function: require_api_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/main.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: run_completeness_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/engine.py:466
low System graph software Dead code conf 1.00 Possibly dead Python function: run_daily_supervisor_report
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/engine.py:406
low System graph software Dead code conf 1.00 Possibly dead Python function: run_gold_bootstrap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/gold_engine.py:90
low System graph software Dead code conf 1.00 Possibly dead Python function: run_gold_maintainer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/gold_engine.py:181
low System graph software Dead code conf 1.00 Possibly dead Python function: run_gold_refresh
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/gold_engine.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: run_holehe
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/scripts/osint/osint_orchestrator.py:118
low System graph software Dead code conf 1.00 Possibly dead Python function: run_maintainer_check
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/engine.py:548
low System graph software Dead code conf 1.00 Possibly dead Python function: run_neo4j_rebuild
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/neo4j_sync.py:249
low System graph software Dead code conf 1.00 Possibly dead Python function: run_osint_enrichment_nightly
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/engine.py:312
low System graph software Dead code conf 1.00 Possibly dead Python function: run_silver_bootstrap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/silver_engine.py:126
low System graph software Dead code conf 1.00 Possibly dead Python function: run_silver_maintainer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/silver_engine.py:315
low System graph software Dead code conf 1.00 Possibly dead Python function: run_silver_refresh
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/platform/ingestion/silver_engine.py:142
low System graph software Dead code conf 1.00 Possibly dead Python function: write_credential
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
infrastructure/agents/signup/signup_agent/main.py:69
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/app/copilot/page.tsx:302
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/app/page.tsx:122
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/tests/e2e/clickables-exhaustive.spec.ts:187
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: GET /_introspect
`backend/routers/datalake.py` declares `GET /_introspect` 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 /_scoring_detail_legacy/{siren}
`backend/routers/datalake.py` declares `GET /_scoring_detail_legacy/{siren}` 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 /agent-actions
`backend/routers/datalake.py` declares `GET /agent-actions` 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 /agents
`infrastructure/agents/platform/main.py` declares `GET /agents` 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 /agents/{name}
`infrastructure/agents/platform/main.py` declares `GET /agents/{name}` 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/enrich-batch
`backend/main.py` declares `GET /api/admin/enrich-batch` 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/index-stats
`backend/main.py` declares `GET /api/admin/index-stats` 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/rebuild-index
`backend/main.py` declares `GET /api/admin/rebuild-index` 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/refresh-db
`backend/main.py` declares `GET /api/admin/refresh-db` 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/graph
`backend/main.py` declares `GET /api/graph` 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
`backend/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/pappers/bodacc/{siren}
`backend/main.py` declares `GET /api/pappers/bodacc/{siren}` 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/pappers/company/{siren}
`backend/main.py` declares `GET /api/pappers/company/{siren}` 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/pappers/concurrents/{siren}
`backend/main.py` declares `GET /api/pappers/concurrents/{siren}` 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/pappers/dirigeant/search
`backend/main.py` declares `GET /api/pappers/dirigeant/search` 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/pappers/dirigeants/{siren}
`backend/main.py` declares `GET /api/pappers/dirigeants/{siren}` 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/pappers/procedures/{siren}
`backend/main.py` declares `GET /api/pappers/procedures/{siren}` 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/pappers/score/{siren}
`backend/main.py` declares `GET /api/pappers/score/{siren}` 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/pappers/search-edrcf
`backend/main.py` declares `GET /api/pappers/search-edrcf` 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/pappers/siren/{siren}
`backend/main.py` declares `GET /api/pappers/siren/{siren}` 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/pappers/statut/{siren}
`backend/main.py` declares `GET /api/pappers/statut/{siren}` 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/sectors
`backend/main.py` declares `GET /api/sectors` 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/targets/search-pappers
`backend/main.py` declares `GET /api/targets/search-pappers` 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
`backend/routers/datalake.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 /dirigeant/{nom}/{prenom}
`backend/routers/datalake.py` declares `GET /dirigeant/{nom}/{prenom}` 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 /dirigeant/{nom}/{prenom}/{date_naissance}
`backend/routers/datalake.py` declares `GET /dirigeant/{nom}/{prenom}/{date_naissance}` 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: GET /fiche/{siren}
`backend/routers/datalake.py` declares `GET /fiche/{siren}` 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 /graph
`backend/routers/datalake.py` declares `GET /graph` 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 /graph/{siren}
`backend/routers/datalake.py` declares `GET /graph/{siren}` 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 /groupe-filiation/{siren}
`backend/routers/datalake.py` declares `GET /groupe-filiation/{siren}` 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 /groupe/{siren}
`backend/routers/datalake.py` declares `GET /groupe/{siren}` 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 /ingestion/freshness
`infrastructure/agents/platform/main.py` declares `GET /ingestion/freshness` 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 /ingestion/sources
`infrastructure/agents/platform/main.py` declares `GET /ingestion/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 /ingestion/specs
`infrastructure/agents/platform/main.py` declares `GET /ingestion/specs` 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 /ingestion/specs/{source_id}
`infrastructure/agents/platform/main.py` declares `GET /ingestion/specs/{source_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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /models
`infrastructure/agents/platform/main.py` declares `GET /models` 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 /pitch-pdf/{siren}
`backend/routers/datalake.py` declares `GET /pitch-pdf/{siren}` 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 /pitch/{siren}
`backend/routers/datalake.py` declares `GET /pitch/{siren}` 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 /scoring/{siren}
`backend/routers/datalake.py` declares `GET /scoring/{siren}` 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 /tables
`backend/routers/datalake.py` declares `GET /tables` 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 /agents/openclaw/run
`infrastructure/agents/platform/main.py` declares `POST /agents/openclaw/run` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /agents/reload
`infrastructure/agents/platform/main.py` declares `POST /agents/reload` 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 /agents/source-hunter/hunt/{source_id}
`infrastructure/agents/platform/main.py` declares `POST /agents/source-hunter/hunt/{source_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: POST /agents/{name}/invoke
`infrastructure/agents/platform/main.py` declares `POST /agents/{name}/invoke` 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/copilot/redteam
`backend/main.py` declares `POST /api/copilot/redteam` 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/refresh-targets
`backend/main.py` declares `POST /api/refresh-targets` 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 /ingestion/discover/{source_id}
`infrastructure/agents/platform/main.py` declares `POST /ingestion/discover/{source_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ingestion/generate/{source_id}
`infrastructure/agents/platform/main.py` declares `POST /ingestion/generate/{source_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ingestion/run/{source_id}
`infrastructure/agents/platform/main.py` declares `POST /ingestion/run/{source_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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /models/{name:path}/pull
`infrastructure/agents/platform/main.py` declares `POST /models/{name:path}/pull` 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 quality Complexity conf 1.00 Very large file: backend/clients/deepseek.py (1641 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/main.py (3046 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/routers/datalake.py (5297 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/dem/ChatPanel.tsx (1166 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/dem/TargetSheet.tsx (1614 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: infrastructure/agents/platform/ingestion/silver_codegen.py (1209 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/99aaf2f3-5e3f-4a97-b68a-db80e1892c15/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/99aaf2f3-5e3f-4a97-b68a-db80e1892c15/

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.