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

vredin/osint

https://github.com/vredin/osint · scanned 2026-06-16 00:53 UTC (2 months, 1 week ago)

174 raw signals (17 security + 157 graph)

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

Complete repo analysis

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

JSON
Combined
68.3
/100
Security checks
68
9 findings
System graph
68
100.0% cov · 138 findings
Critical
5
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 5 High 12 Medium 11 Low 86 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 9 System graph 138 Crowd 0 Layer: Quality 70 Cicd 1 Security 16 Software 6 Frontend 2 Hardware 2 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 68.3/100 with 100.0% coverage. It contains 7685 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 157 findings — concentrated in quality (78), api (50), security (18). Risk profile is high: 5 critical, 9 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 114 of 147 actionable findings. 223 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 Security checks cicd CI/CD security conf 0.86 6 occurrences Foundry mined claimed resolved with failing ci: vredin/osint
Graph query export: Claimed resolved with failing CI Query id: claimed_resolved_with_failing_ci Query type: motif_query Intent: Hard negatives where CI/failure evidence contradicts a resolution claim. Motif: claimed_resolved_with_failing_ci Training usage: hard_negative Graph gold label: contradict…
6 occurrences
repo-level (6 hits)
CI/CD securityCI/CD
critical Security checks quality Practices conf 0.82 9 occurrences Foundry mined mock as real or placeholder: vredin/osint
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
9 occurrences
repo-level (9 hits)
critical Security checks security auth conf 0.78 4 occurrences Foundry mined security auth guardrail gaps: vredin/osint
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
4 occurrences
repo-level (4 hits)
critical System graph security Secrets conf 1.00 4 occurrences Possible secret in scripts/pg_init.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 26, 58, 59, 60
scripts/pg_init.sh:26, 58, 59, 60 (4 hits)
critical System graph security Secrets conf 1.00 Possible secret in tmp/OSINTBOT/config.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
tmp/OSINTBOT/config.py:23
high Security checks quality Practices conf 0.84 15 occurrences Foundry mined bad chains: vredin/osint
Comment chain pattern product: bad_chains Repo: vredin/osint Thread: vredin/osint#9 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_verifica…
15 occurrences
repo-level (15 hits)
high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: vredin/osint
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: assumption_check Repo: vredin/osint T…
2 occurrences
repo-level (2 hits)
high Security checks quality Testing conf 0.78 3 occurrences Foundry mined test ci gap after feedback: vredin/osint
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: weak_supervision_needs_…
3 occurrences
repo-level (3 hits)
high System graph security auth conf 1.00 FastAPI POST `biometric_search` without auth dependency — src/routers/cases.py:574
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/routers/cases.py:574 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `refresh_tokens` without auth dependency — src/routers/auth.py:358
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/routers/auth.py:358 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `telegram_webhook` without auth dependency — src/routers/telegram_webhook.py:32
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/routers/telegram_webhook.py:32 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_polygraphy` without auth dependency — src/routers/cases.py:560
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/routers/cases.py:560 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `work_block_add` without auth dependency — src/admin/work_cases.py:397
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/admin/work_cases.py:397 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `work_block_delete` without auth dependency — src/admin/work_cases.py:528
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/admin/work_cases.py:528 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `work_block_save` without auth dependency — src/admin/work_cases.py:463
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/admin/work_cases.py:463 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `save_annotations` without auth dependency — src/routers/dossier_edit.py:383
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/routers/dossier_edit.py:383 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in src/admin/static/htmx.min.js:1
Found a known-risky pattern (new_function_used). Review and replace if possible.
src/admin/static/htmx.min.js:1 New function used
medium Security checks quality Practices conf 0.62 5 occurrences Foundry mined assumption checks: vredin/osint
Comment chain pattern product: assumption_checks Repo: vredin/osint Thread: vredin/osint#5 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_has_real_artifacts, source_graph_has_veri…
5 occurrences
repo-level (5 hits)
medium Security checks quality maintenance conf 0.70 5 occurrences Foundry mined blueprint gap alignment: vredin/osint
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
5 occurrences
repo-level (5 hits)
medium Security checks quality Practices conf 0.70 17 occurrences Foundry mined unresolved feedback: vredin/osint
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
17 occurrences
repo-level (17 hits)
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/admin/static/htmx.min.js:1
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/admin/static/htmx.min.js:1 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/routers/accept_invite.py:183
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/routers/accept_invite.py:183 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in src/admin/static/htmx.min.js:1
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
src/admin/static/htmx.min.js:1 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in src/admin/static/htmx.min.js:1
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
src/admin/static/htmx.min.js:1 Insert adjacent html
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/check_dpia_artifacts.py:27
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 30 placeholder/mock markers across 14 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 29 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `APP_BASE_URL`, `APP_ENV`, `BREVO_SENDER_ADDRESS`, `BREVO_SMTP_KEY`, `BREVO_SMTP_LOGIN`, `BUDGET_OVERRUN_TOLERANCE_USD`, `DATA_GOV_UA_COURT_RESOURCE_ID`, `DB_IMPORT_URL` + 21 more. Add them (with a placeholder/comment) to .env.example so onboarding…
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 86 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 2 occurrences 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.
lines 2, 15
Dockerfile:2, 15 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 16 places
Functions with the same first-5-line body hash: src/adapters/osint_services.py:search, src/adapters/osint_services.py:search, src/adapters/osint_services.py:search, src/adapters/osint_services.py:search This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.h…
duplicatesduplication
low System graph quality Integrity conf 1.00 7 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: tmp/OSINTBOT/services/hudson_checker.py:run_hudson_check_sync, tmp/OSINTBOT/services/hudson_checker.py:run_hudson_check This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or …
7 occurrences
repo-level (7 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: alembic/versions/20260612_0092_compliance_cases_create_permission.py:upgrade, alembic/versions/20260612_0092_compliance_cases_create_permission.py:downgrade, alembic/versions/20260602_0080_work_section_compliance_security_permissions.py:downgrade Thi…
10 occurrences
repo-level (10 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: src/admin/router.py:users_list, src/admin/router.py:invite_form, src/admin/router.py:sources_list, src/admin/router.py:source_create_action This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygie…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: src/admin/router.py:dashboard_system_status, src/admin/router.py:llm_cost_dashboard, src/admin/router.py:pdf_settings_page, src/admin/router.py:dossier_link_settings_page This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — …
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 `all_old` in tests/unit/admin/managers/test_user_provisioning.py:729
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 `audit_log_v2` in tests/unit/test_check_audit_migration.py:206
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 `config_sources_backup` in alembic/versions/20260511_0008_config_sources.py:201
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 `env_backup` in tests/unit/test_invite.py:372
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 `pep_check_v1` in alembic/versions/20260511_0010_config_risk_rules.py:54
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 `pep_check_v1` in tests/unit/risk/test_rule_parser.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 `pgbackrest_full_backup` in src/tasks/backup.py:8
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 `pgbackrest_full_backup` in src/worker/beat_schedule.py:103
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 `pgbackrest_full_backup` in tests/unit/tasks/test_backup_tasks.py:18
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_error_renders_without_link_or_copy` in tests/unit/admin/test_templates.py:500
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 `unknown_adapter_v2` in tests/unit/reports/test_degraded_badge.py:59
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: add_telegram_account
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/database/telegram_operations.py:384
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_telegram_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/handlers/telegram.py:177
low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_telegram_input
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/utils/validators.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: run_hudson_check_sync
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/services/hudson_checker.py:17
low System graph software Dead code conf 1.00 Possibly dead Python function: search_telegram_accounts_by_phone
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/database/telegram_operations.py:285
low System graph software Dead code conf 1.00 Possibly dead Python function: search_telegram_accounts_by_username
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tmp/OSINTBOT/database/telegram_operations.py:316
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 — src/admin/static/htmx.min.js:1
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 quality Integrity conf 1.00 Stub function `downgrade` (body is just `pass`/`return`) — alembic/versions/20260511_0000_baseline.py:30
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `increment_general_count` (body is just `pass`/`return`) — tmp/OSINTBOT/handlers/telegram.py:152
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `upgrade` (body is just `pass`/`return`) — alembic/versions/20260511_0001_extensions_searchpath.py:20
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /settings/api-keys/{source_id}/key
`src/admin/router.py` declares `DELETE /settings/api-keys/{source_id}/key` 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 /
`src/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /activity
`src/admin/router.py` declares `GET /activity` 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/totp-grace-status
`src/admin/router.py` declares `GET /api/totp-grace-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: GET /audit/integrity-check/
`src/admin/router.py` declares `GET /audit/integrity-check/` 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 /dsar/approvals
`src/admin/router.py` declares `GET /dsar/approvals` 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 /llm-cost/
`src/admin/router.py` declares `GET /llm-cost/` 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 /login
`src/admin/router.py` declares `GET /login` 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 /partials/totp-grace-form
`src/admin/router.py` declares `GET /partials/totp-grace-form` 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 /risk-rules/
`src/admin/router.py` declares `GET /risk-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 /risk-rules/{rule_id}
`src/admin/router.py` declares `GET /risk-rules/{rule_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 /settings/
`src/admin/router.py` declares `GET /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 api Wiring conf 1.00 Unused endpoint: GET /settings/dossier-link/
`src/admin/router.py` declares `GET /settings/dossier-link/` 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 /settings/pdf/
`src/admin/router.py` declares `GET /settings/pdf/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /sources/
`src/admin/router.py` declares `GET /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 /sources/create-form
`src/admin/router.py` declares `GET /sources/create-form` 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 /sources/{source_id}/edit-form
`src/admin/router.py` declares `GET /sources/{source_id}/edit-form` 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 /sources/{source_id}/row
`src/admin/router.py` declares `GET /sources/{source_id}/row` 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 /stats
`src/admin/router.py` declares `GET /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 /system-status
`src/admin/router.py` declares `GET /system-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: GET /telegram-settings
`src/admin/router.py` declares `GET /telegram-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 api Wiring conf 1.00 Unused endpoint: GET /totp/setup
`src/admin/router.py` declares `GET /totp/setup` 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 /users/
`src/admin/router.py` declares `GET /users/` 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 /users/invite-form
`src/admin/router.py` declares `GET /users/invite-form` 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 /users/rows
`src/admin/router.py` declares `GET /users/rows` 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 /users/{user_id}/access
`src/admin/router.py` declares `GET /users/{user_id}/access` 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/sources/{source_id}/trust-score
`src/admin/router.py` declares `PATCH /api/sources/{source_id}/trust-score` 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 /config/dossier_link_settings
`src/admin/router.py` declares `PATCH /config/dossier_link_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 api Wiring conf 1.00 Unused endpoint: PATCH /config/llm_budget
`src/admin/router.py` declares `PATCH /config/llm_budget` 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 /config/pdf_watermark_type
`src/admin/router.py` declares `PATCH /config/pdf_watermark_type` 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 /risk-rules/{rule_id}
`src/admin/router.py` declares `PATCH /risk-rules/{rule_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /sources/{source_id}/toggle-action
`src/admin/router.py` declares `PATCH /sources/{source_id}/toggle-action` 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 /users/{user_id}/role-action
`src/admin/router.py` declares `PATCH /users/{user_id}/role-action` 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 /config/telegram_totp_hours
`src/admin/router.py` declares `POST /config/telegram_totp_hours` 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 /dsar/{request_id}/approve
`src/admin/router.py` declares `POST /dsar/{request_id}/approve` 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 /invites/{invite_id}/resend-action
`src/admin/router.py` declares `POST /invites/{invite_id}/resend-action` 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 /invites/{invite_id}/revoke-action
`src/admin/router.py` declares `POST /invites/{invite_id}/revoke-action` 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 /login-action
`src/admin/router.py` declares `POST /login-action` 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 /logout
`src/admin/router.py` declares `POST /logout` 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 /set-language
`src/admin/router.py` declares `POST /set-language` 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 /settings/api-keys/{source_id}/key
`src/admin/router.py` declares `POST /settings/api-keys/{source_id}/key` 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 /settings/totp-grace-period
`src/admin/router.py` declares `POST /settings/totp-grace-period` 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 /sources/create-action
`src/admin/router.py` declares `POST /sources/create-action` 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 /sources/{source_id}/edit-action
`src/admin/router.py` declares `POST /sources/{source_id}/edit-action` 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 /totp/setup-action
`src/admin/router.py` declares `POST /totp/setup-action` 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 /users/invite-action
`src/admin/router.py` declares `POST /users/invite-action` 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 /users/{user_id}/access
`src/admin/router.py` declares `POST /users/{user_id}/access` 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 /users/{user_id}/deactivate-action
`src/admin/router.py` declares `POST /users/{user_id}/deactivate-action` 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 /users/{user_id}/tg-link-action
`src/admin/router.py` declares `POST /users/{user_id}/tg-link-action` 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 /users/{user_id}/tg-unlink-action
`src/admin/router.py` declares `POST /users/{user_id}/tg-unlink-action` 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: src/admin/router.py (5267 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/admin/work_lookup.py (1802 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/admin/test_offline_db_screen.py (1500 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/unit/admin/test_users_screen.py (1846 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/796b8e94-228a-459d-8f48-cf7bcb7222ea/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/796b8e94-228a-459d-8f48-cf7bcb7222ea/

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.