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

squall321/SignalForge

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

202 raw signals (0 security + 202 graph)

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

Complete repo analysis

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

JSON
Combined
63.9
/100
Security checks
64
0 findings
System graph
64
100.0% cov · 170 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 12 Medium 8 Low 114 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 170 Crowd 0 Layer: Software 19 Frontend 1 Network 3 Security 14 Cicd 1 Quality 82 Api 50
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 63.9/100 with 100.0% coverage. It contains 5526 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 202 findings — concentrated in quality (102), api (50), software (26). Risk profile is high: 1 critical, 12 high, 11 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 133 of 170 actionable findings. 202 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 crawler/platforms/mybroadband.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
crawler/platforms/mybroadband.py:61
high System graph security auth conf 1.00 FastAPI DELETE `delete_rule` without auth dependency — backend/app/api/alerts.py:431
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/alerts.py:431 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_rule` without auth dependency — backend/app/api/alerts.py:387
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/alerts.py:387 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `apply_presets` without auth dependency — backend/app/api/alerts.py:450
`@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/app/api/alerts.py:450 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `cache_warm` without auth dependency — backend/app/api/_internal.py:2948
`@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/app/api/_internal.py:2948 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `channels_slack_test` without auth dependency — backend/app/api/alerts.py:552
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/app/api/alerts.py:552 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `compare_llm` without auth dependency — backend/app/api/insights.py:103
`@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/app/api/insights.py:103 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_rule` without auth dependency — backend/app/api/alerts.py:352
`@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/app/api/alerts.py:352 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `export_pdf_endpoint` without auth dependency — backend/app/api/_internal.py:2629
`@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/app/api/_internal.py:2629 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fire_test` without auth dependency — backend/app/api/alerts.py:588
`@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/app/api/alerts.py:588 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `llm_narrative` without auth dependency — backend/app/api/temporal.py:82
`@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/app/api/temporal.py:82 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `share_token_create` without auth dependency — backend/app/api/_internal.py:2674
`@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/app/api/_internal.py:2674 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_crawl` without auth dependency — backend/app/api/crawl_jobs.py:21
`@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/app/api/crawl_jobs.py:21 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/global/CommandPalette.tsx:4
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 quality Integrity conf 1.00 4 occurrences Frontend route `/collection` has no Link/navigate to it — frontend/src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
4 occurrences
repo-level (4 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in signalforge_platform.html:462
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
signalforge_platform.html:462 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 25 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 252 in use
Port 252 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/_common.sh Ports
low System graph quality Integrity conf 1.00 181 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AIDH_DEAD_LETTER_DIR`, `ALERTS_API_URL`, `ALERT_PROVIDER`, `ALERT_WEBHOOK_URL`, `AUDIT_BACKUP_RISK_WITH_PRESERVE`, `AUDIT_DRY_RUN_ERROR_RISK`, `AUDIT_INSERT_ONLY_SCRIPTS`, `AUDIT_MIN_RUNS_FOR_ALERT` + 173 more. Add them (with a placeholder/comment…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 119 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 6 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.
2 files, 6 locations
.github/workflows/qa.yml:31, 70, 90, 115 (4 hits)
.github/workflows/deploy.yml:29, 32 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: crawler/platforms/androidpolice.py:crawl, crawler/platforms/tomsguide.py:crawl This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: crawler/platforms/nu_nl.py:crawl, crawler/platforms/sspai.py:crawl, crawler/platforms/iphoneincanada.py:crawl This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document w…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: crawler/platforms/resetera.py:crawl, crawler/platforms/notebookcheck.py:crawl, crawler/platforms/hwupgrade.py:crawl, crawler/platforms/ifixit.py:crawl This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
2 occurrences
repo-level (2 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 `_write_backup` in crawler/scripts/sentiment_backfill.py:109
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 `_write_backup` in crawler/scripts/topic_backfill.py:117
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 `_write_delete_backup` in crawler/scripts/dedup_voc.py:96
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 `build_prompt_v2` in crawler/tests/test_topic_llm_apply_v2.py:4
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 `crisis_backfill_v2` in crawler/scripts/crisis_platform_backfill.py:9
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 `crisis_backfill_v2` in crawler/tests/test_crisis_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `d_old` in crawler/scripts/korean_pagination_deep.py:194
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 `harvest_week_report_v2` in crawler/insight/harvest_week_report_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 `harvest_week_report_v2` in crawler/tests/test_weekly_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `missing_legacy` in crawler/tests/test_hackernews_search_v3.py:119
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 `model_copy` in backend/app/services/temporal_service.py:235
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 `p_copy` in crawler/platforms/gsmarena.py:242
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 `p_copy` in crawler/platforms/gsmarena_forum.py:221
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 `prompt_v2` in crawler/tests/test_prompt_v3.py:71
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_crisis_cases_v2` in backend/tests/test_crisis_cases_v2.py:12
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_crisis_v2` in crawler/scripts/crisis_backfill_v2.py:48
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_fold_flip_legacy` in crawler/tests/test_relink.py:43
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_llm_routing_v2` in crawler/tests/test_llm_routing_v2.py:11
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_relink_v2` in crawler/tests/test_relink_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_relink_v2` in crawler/tests/test_relink_v3.py:196
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_rules_v2` in backend/tests/test_rules_v2.py:10
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_system_prompt_v3_is_stronger_than_v2` in crawler/tests/test_llm_v3_prompts.py:33
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_xda_mapping_v2` in crawler/tests/test_xda_mapping_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `topic_eval_v2` in crawler/scripts/topic_eval_v2.py:25
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 `topic_eval_v2` in crawler/tests/test_topic_eval_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `topic_llm_prompt_v2` in crawler/scripts/topic_llm_apply.py:73
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 `topic_llm_prompt_v2` in crawler/scripts/topic_llm_prompt_v2.py:1
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `verify_backup` in backend/app/api/_internal.py:1080
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 `verify_backup` in backend/tests/test_alerts_metric_path.py:29
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 `verify_backup` in crawler/celery_app.py:358
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 `verify_backup` in crawler/tasks.py:929
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: broadcast_new_voc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/api/websocket.py:50
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.
backend/app/core/cache.py:145
low System graph software Dead code conf 1.00 Possibly dead Python function: do_run_migrations
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/alembic/env.py:47
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
backend/alembic/versions/0009_products_release_boost.py:132
backend/alembic/versions/0011_voc_unmapped_reason.py:52
backend/alembic/versions/0014_galaxy_master_timeline_mv.py:62
backend/alembic/versions/0015_reddit_rss_platform.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: fmt_pct
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/reports/_common.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/nlp/topic_classifier.py:443
low System graph software Dead code conf 1.00 Possibly dead Python function: repl
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
integrations/aidatahub/aidatahub_sync.py:408
low System graph software Dead code conf 1.00 Possibly dead Python function: run_bobae
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_backfill_v2.py:471
low System graph software Dead code conf 1.00 Possibly dead Python function: run_bobae
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:284
low System graph software Dead code conf 1.00 Possibly dead Python function: run_dcinside
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:228
low System graph software Dead code conf 1.00 Possibly dead Python function: run_fmk
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_backfill_v2.py:515
low System graph software Dead code conf 1.00 Possibly dead Python function: run_fmk
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:328
low System graph software Dead code conf 1.00 Possibly dead Python function: run_hackernews
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_backfill_v2.py:462
low System graph software Dead code conf 1.00 Possibly dead Python function: run_mlbpark
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:350
low System graph software Dead code conf 1.00 Possibly dead Python function: run_ppomppu
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:256
low System graph software Dead code conf 1.00 Possibly dead Python function: run_ruli
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_backfill_v2.py:493
low System graph software Dead code conf 1.00 Possibly dead Python function: run_ruli
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
crawler/scripts/crisis_platform_backfill.py:306
low System graph software Dead code conf 1.00 Possibly dead Python function: set_rules
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/app/core/alerts/engine.py:77
low System graph software Dead code conf 1.00 5 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
5 files, 5 locations
backend/alembic/versions/0009_products_release_boost.py:103
backend/alembic/versions/0011_voc_unmapped_reason.py:35
backend/alembic/versions/0012_voc_topics.py:25
backend/alembic/versions/0014_galaxy_master_timeline_mv.py:55
backend/alembic/versions/0015_reddit_rss_platform.py:22
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/__tests__/mobile_audit.test.ts:143
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 /api/v1
`backend/app/api/products.py` declares `GET /api/v1` 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/v1/anomaly-context
`backend/app/api/deep.py` declares `GET /api/v1/anomaly-context` 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/v1/anomaly-drilldown
`backend/app/api/deep.py` declares `GET /api/v1/anomaly-drilldown` 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/v1/anomaly-drilldown-hour
`backend/app/api/deep.py` declares `GET /api/v1/anomaly-drilldown-hour` 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/v1/anomaly-with-drivers
`backend/app/api/deep.py` declares `GET /api/v1/anomaly-with-drivers` 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/v1/category-momentum
`backend/app/api/deep.py` declares `GET /api/v1/category-momentum` 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/v1/category-product-matrix
`backend/app/api/deep.py` declares `GET /api/v1/category-product-matrix` 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/v1/country-sentiment-gap
`backend/app/api/deep.py` declares `GET /api/v1/country-sentiment-gap` 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/v1/crisis-cases
`backend/app/api/deep.py` declares `GET /api/v1/crisis-cases` 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/v1/engagement-sentiment
`backend/app/api/deep.py` declares `GET /api/v1/engagement-sentiment` 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/v1/galaxy-timeline
`backend/app/api/deep.py` declares `GET /api/v1/galaxy-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 /api/v1/graph
`backend/app/api/kg.py` declares `GET /api/v1/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/v1/influence-rank
`backend/app/api/deep.py` declares `GET /api/v1/influence-rank` 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/v1/issue-lifecycle
`backend/app/api/deep.py` declares `GET /api/v1/issue-lifecycle` 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/v1/keyword-cooccurrence
`backend/app/api/deep.py` declares `GET /api/v1/keyword-cooccurrence` 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/v1/keyword-detail
`backend/app/api/deep.py` declares `GET /api/v1/keyword-detail` 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/v1/keyword-network
`backend/app/api/deep.py` declares `GET /api/v1/keyword-network` 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/v1/lifecycle-funnel
`backend/app/api/deep.py` declares `GET /api/v1/lifecycle-funnel` 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/v1/new-term-survival
`backend/app/api/deep.py` declares `GET /api/v1/new-term-survival` 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/v1/node/{node_id}/samples
`backend/app/api/kg.py` declares `GET /api/v1/node/{node_id}/samples` 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/v1/overview
`backend/app/api/dashboard.py` declares `GET /api/v1/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/v1/platforms
`backend/app/main.py` declares `GET /api/v1/platforms` 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/v1/platforms/anomalies
`backend/app/api/community.py` declares `GET /api/v1/platforms/anomalies` 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/v1/platforms/clusters
`backend/app/api/community.py` declares `GET /api/v1/platforms/clusters` 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/v1/platforms/dispersion
`backend/app/api/community.py` declares `GET /api/v1/platforms/dispersion` 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/v1/platforms/early-signal
`backend/app/api/community.py` declares `GET /api/v1/platforms/early-signal` 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/v1/platforms/health
`backend/app/api/community.py` declares `GET /api/v1/platforms/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/v1/platforms/product-matrix
`backend/app/api/community.py` declares `GET /api/v1/platforms/product-matrix` 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/v1/product-funnel
`backend/app/api/deep.py` declares `GET /api/v1/product-funnel` 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/v1/rules
`backend/app/api/alerts.py` declares `GET /api/v1/rules` 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/v1/search
`backend/app/api/kg.py` declares `GET /api/v1/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/v1/sentiment-driver
`backend/app/api/deep.py` declares `GET /api/v1/sentiment-driver` 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/v1/series-comparison
`backend/app/api/deep.py` declares `GET /api/v1/series-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 /api/v1/site-diffusion
`backend/app/api/deep.py` declares `GET /api/v1/site-diffusion` 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/v1/temporal-compare
`backend/app/api/temporal.py` declares `GET /api/v1/temporal-compare` 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/v1/temporal-series
`backend/app/api/temporal.py` declares `GET /api/v1/temporal-series` 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/v1/{code}/stats
`backend/app/api/products.py` declares `GET /api/v1/{code}/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/v1/{code}/voc
`backend/app/api/products.py` declares `GET /api/v1/{code}/voc` 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/v1/{token}
`backend/app/api/shared.py` declares `GET /api/v1/{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 /category-dist
`backend/app/api/analytics.py` declares `GET /category-dist` 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 /cohort-compare
`backend/app/api/analytics.py` declares `GET /cohort-compare` 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 /compare
`backend/app/api/analytics.py` declares `GET /compare` 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 /country-heatmap
`backend/app/api/analytics.py` declares `GET /country-heatmap` 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 /keyword-track
`backend/app/api/analytics.py` declares `GET /keyword-track` 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 /recent-issues
`backend/app/api/analytics.py` declares `GET /recent-issues` 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 /sentiment-trend
`backend/app/api/analytics.py` declares `GET /sentiment-trend` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /site-health
`backend/app/api/analytics.py` declares `GET /site-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 /top-issues
`backend/app/api/analytics.py` declares `GET /top-issues` 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/v1/llm-narrative
`backend/app/api/temporal.py` declares `POST /api/v1/llm-narrative` 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/v1/rules
`backend/app/api/alerts.py` declares `POST /api/v1/rules` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/app/api/_internal.py (4228 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/app/services/deep_service.py (2788 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crawler/insight/workflow_validator.py (1378 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crawler/scripts/relink_products.py (1242 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crawler/tasks.py (1470 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/8be72b3f-b043-4236-87b3-113eb8887c34/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8be72b3f-b043-4236-87b3-113eb8887c34/

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.