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

selimzenger-source/sz-bist-finans-backend

https://github.com/selimzenger-source/sz-bist-finans-backend · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

170 raw signals (0 security + 170 graph)

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

Complete repo analysis

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

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

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

high System graph quality Integrity conf 1.00 Blocking `httpx.post(...)` inside `async def _generate_index_cover_image` — app/scheduler.py:3369
Sync I/O inside an async function blocks the event loop. While `httpx.post(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
app/scheduler.py:3369 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `httpx.post(...)` inside `async def _generate_kurum_oneri_cover` — app/scheduler.py:6781
Sync I/O inside an async function blocks the event loop. While `httpx.post(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
app/scheduler.py:6781 Sync io in asyncPerformance
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/admin/routes.py:2182
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/admin/routes.py:2182 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/scrapers/resmi_gazete_scraper.py:80
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/scrapers/resmi_gazete_scraper.py:80 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/scrapers/spk_bulletin_scraper.py:415
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/scrapers/spk_bulletin_scraper.py:415 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/scrapers/spk_ihrac_scraper.py:56
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/scrapers/spk_ihrac_scraper.py:56 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/scrapers/spk_scraper.py:36
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/scrapers/spk_scraper.py:36 Tls verify false
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in app/services/mentions_reply_service.py:137
Found a known-risky pattern (weak_hash). Review and replace if possible.
app/services/mentions_reply_service.py:137 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in app/services/twitter_reply_service.py:167
Found a known-risky pattern (weak_hash). Review and replace if possible.
app/services/twitter_reply_service.py:167 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in app/services/twitter_service.py:604
Found a known-risky pattern (weak_hash). Review and replace if possible.
app/services/twitter_service.py:604 Weak hash
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
5 test file(s) for 137 source file(s) (ratio 0.04). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 11 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_TELEGRAM_BOT_TOKEN`, `ADMIN_TELEGRAM_CHAT_ID`, `ANTHROPIC_API_KEY`, `API_URL`, `BIST_ADMIN_PW`, `BIST_API_URL`, `CLOUDINARY_URL`, `FB_PAGE_ACCESS_TOKEN` + 3 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't br…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph 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 106 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.13-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: excel_sync.py:read_matriks_excel_live, excel_sync.py:read_matriks_excel 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.
10 occurrences
repo-level (10 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: app/main.py:clean_text, app/main.py:clean_text, app/main.py:clean_text 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: app/services/capital_increase_processor.py:process_kap_disclosure, app/services/dividend_calendar_processor.py:process_kap_disclosure, app/services/business_deal_processor.py:process_kap_disclosure, app/services/dividend_payment_processor.py:process_k…
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 `ceiling_alerts_v2` in app/admin/routes.py:1871
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 `default_v2` in app/services/broadcast.py:294
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 `default_v2` in app/services/notification.py:126
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 `ipo_alerts_v2` in app/scheduler.py:1374
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 `kap_news_v2` in app/main.py:3270
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `skipped_old` in app/services/news_scanner_service.py:415
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: archive_old_ipos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:970
low System graph software Dead code conf 1.00 Possibly dead Python function: ceiling_update_retry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2980
low System graph software Dead code conf 1.00 Possibly dead Python function: check_morning_tweets
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:1497
low System graph software Dead code conf 1.00 Possibly dead Python function: check_resmi_gazete_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:555
low System graph software Dead code conf 1.00 Possibly dead Python function: check_spk_bulletins_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:541
low System graph software Dead code conf 1.00 Possibly dead Python function: check_trading_start_halkarz
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:1844
low System graph software Dead code conf 1.00 Possibly dead Python function: check_viop_notifications
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:598
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_expired_coupons
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:891
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_notification_logs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:4394
low System graph software Dead code conf 1.00 Possibly dead Python function: cleanup_old_kap_disclosures
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:862
low System graph software Dead code conf 1.00 Possibly dead Python function: generate_missing_ipo_reports
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:803
low System graph software Dead code conf 1.00 Possibly dead Python function: kap_ai_retry_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:3599
low System graph software Dead code conf 1.00 Possibly dead Python function: morning_scraper_run
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:3018
low System graph software Dead code conf 1.00 Possibly dead Python function: news_scanner_breaking_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:6727
low System graph software Dead code conf 1.00 Possibly dead Python function: poll_telegram_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:757
low System graph software Dead code conf 1.00 Possibly dead Python function: push_health_report_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2237
low System graph software Dead code conf 1.00 Possibly dead Python function: scrape_kap_ipo
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:211
low System graph software Dead code conf 1.00 Possibly dead Python function: scrape_kap_news
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:268
low System graph software Dead code conf 1.00 Possibly dead Python function: send_first_trading_day_notifications
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:3066
low System graph software Dead code conf 1.00 Possibly dead Python function: send_last_day_warnings
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:1959
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_company_intro_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2142
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_distribution_morning_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:913
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_last_day_morning_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2103
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_opening_price_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:3137
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_spk_approval_intro_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2023
low System graph software Dead code conf 1.00 Possibly dead Python function: tweet_spk_pending_monthly_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:2194
low System graph software Dead code conf 1.00 Possibly dead Python function: update_bist50_index_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/scheduler.py:3574
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 api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/users/{device_id}
`app/main.py` declares `DELETE /api/v1/users/{device_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/ipos
`app/main.py` declares `GET /api/v1/ipos` 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/ipos/archived
`app/main.py` declares `GET /api/v1/ipos/archived` 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/ipos/sections
`app/main.py` declares `GET /api/v1/ipos/sections` 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/ipos/spk-applications
`app/main.py` declares `GET /api/v1/ipos/spk-applications` 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/ipos/upcoming
`app/main.py` declares `GET /api/v1/ipos/upcoming` 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/ipos/{ipo_id}
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/ipos/{ipo_id}/poll-my-vote
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}/poll-my-vote` 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/ipos/{ipo_id}/poll-phase
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}/poll-phase` 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/ipos/{ipo_id}/poll-stats
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}/poll-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/ipos/{ipo_id}/prospectus-analysis
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}/prospectus-analysis` 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/ipos/{ipo_id}/prospectus-image
`app/main.py` declares `GET /api/v1/ipos/{ipo_id}/prospectus-image` 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/news
`app/main.py` declares `GET /api/v1/news` 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/news-tiers
`app/main.py` declares `GET /api/v1/news-tiers` 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/news/latest
`app/main.py` declares `GET /api/v1/news/latest` 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/notification-tiers
`app/main.py` declares `GET /api/v1/notification-tiers` 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/public/blogs
`app/main.py` declares `GET /api/v1/public/blogs` 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/public/blogs/{slug}
`app/main.py` declares `GET /api/v1/public/blogs/{slug}` 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/public/daily-market-stats
`app/main.py` declares `GET /api/v1/public/daily-market-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/public/news-feed
`app/main.py` declares `GET /api/v1/public/news-feed` 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/public/spk-bulletin-analyses
`app/main.py` declares `GET /api/v1/public/spk-bulletin-analyses` 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/public/stock-price/{ticker}
`app/main.py` declares `GET /api/v1/public/stock-price/{ticker}` 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/public/stock-prices
`app/main.py` declares `GET /api/v1/public/stock-prices` 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/public/system-announcements
`app/main.py` declares `GET /api/v1/public/system-announcements` 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/public/viop-night-session
`app/main.py` declares `GET /api/v1/public/viop-night-session` 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/telegram-news
`app/main.py` declares `GET /api/v1/telegram-news` 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/telegram-news/locked-teasers
`app/main.py` declares `GET /api/v1/telegram-news/locked-teasers` 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/users/{device_id}
`app/main.py` declares `GET /api/v1/users/{device_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/users/{device_id}/stock-notifications
`app/main.py` declares `GET /api/v1/users/{device_id}/stock-notifications` 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/users/{device_id}/subscription
`app/main.py` declares `GET /api/v1/users/{device_id}/subscription` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/users/{device_id}/stock-notifications/deactivate-all
`app/main.py` declares `PATCH /api/v1/users/{device_id}/stock-notifications/deactivate-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/users/{device_id}/stock-notifications/{sub_id}/mute
`app/main.py` declares `PATCH /api/v1/users/{device_id}/stock-notifications/{sub_id}/mute` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/activate-news-subscription/{device_id}
`app/main.py` declares `POST /api/v1/admin/activate-news-subscription/{device_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/cleanup-spk-names
`app/main.py` declares `POST /api/v1/admin/cleanup-spk-names` 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/admin/deactivate-stock-notification/{sub_id}
`app/main.py` declares `POST /api/v1/admin/deactivate-stock-notification/{sub_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/admin/generate-blog
`app/main.py` declares `POST /api/v1/admin/generate-blog` 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/admin/generate-spk-descriptions
`app/main.py` declares `POST /api/v1/admin/generate-spk-descriptions` 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/admin/service-status
`app/main.py` declares `POST /api/v1/admin/service-status` 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/admin/test-gemini
`app/main.py` declares `POST /api/v1/admin/test-gemini` 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/admin/toggle-kill-switch
`app/main.py` declares `POST /api/v1/admin/toggle-kill-switch` 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/admin/update-bulletin-text
`app/main.py` declares `POST /api/v1/admin/update-bulletin-text` 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/admin/verify
`app/main.py` declares `POST /api/v1/admin/verify` 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/client-error
`app/main.py` declares `POST /api/v1/client-error` 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/ipos/{ipo_id}/poll-vote
`app/main.py` declares `POST /api/v1/ipos/{ipo_id}/poll-vote` 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/telegram-news/test-send
`app/main.py` declares `POST /api/v1/telegram-news/test-send` 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/users/register
`app/main.py` declares `POST /api/v1/users/register` 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/users/{device_id}/stock-notifications
`app/main.py` declares `POST /api/v1/users/{device_id}/stock-notifications` 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/users/{device_id}/stock-notifications/sync
`app/main.py` declares `POST /api/v1/users/{device_id}/stock-notifications/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/users/{device_id}
`app/main.py` declares `PUT /api/v1/users/{device_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/v1/users/{device_id}/reminder-settings
`app/main.py` declares `PUT /api/v1/users/{device_id}/reminder-settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: app/admin/routes.py (6003 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/main.py (20384 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/scheduler.py (7657 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/scrapers/halkarz_scraper.py (1371 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/scrapers/spk_bulletin_scraper.py (1146 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/scrapers/telegram_poller.py (2461 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/ai_ipo_analyzer.py (1280 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/ai_market_report.py (2049 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/ai_news_scorer.py (4504 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/chart_image_generator.py (3119 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/dividend_calendar_processor.py (1367 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/market_close_analyzer.py (1372 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/news_scanner_service.py (1772 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/notification.py (2161 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/prospectus_analyzer.py (1833 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/twitter_reply_service.py (1770 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/services/twitter_service.py (4146 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: excel_sync.py (1336 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/c1d3db15-5d28-472f-bc16-5270f56cfb60/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c1d3db15-5d28-472f-bc16-5270f56cfb60/

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.