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

zcor/strongasan0x

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

105 raw signals (0 security + 105 graph)

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

Complete repo analysis

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

JSON
Combined
59.6
/100
Security checks
60
0 findings
System graph
60
88.9% cov · 89 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 0 Medium 32 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 89 Crowd 0 Layer: Software 6 Frontend 1 Quality 36 Security 9 Api 37
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 59.6/100 with 88.9% coverage. It contains 916 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 105 findings — concentrated in quality (52), api (37), security (9). Risk profile is low: 0 critical, 0 high, 33 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 81 of 89 actionable findings. 105 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.

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
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 auth conf 1.00 Django view `api_messages` may be unauthenticated — discord_dashboard/dashboard/views.py:135
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
discord_dashboard/dashboard/views.py:135 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_stats` may be unauthenticated — discord_dashboard/dashboard/views.py:177
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
discord_dashboard/dashboard/views.py:177 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `landing` may be unauthenticated — rollcall/views.py:243
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/views.py:243 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `link_strava` may be unauthenticated — rollcall/warrior/views.py:405
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/warrior/views.py:405 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `strava_callback` may be unauthenticated — rollcall/warrior/views.py:424
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/warrior/views.py:424 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `telegram_callback` may be unauthenticated — rollcall/warrior/views.py:105
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/warrior/views.py:105 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `telegram_webhook` may be unauthenticated — rollcall/views.py:375
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/views.py:375 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `warrior_dashboard` may be unauthenticated — rollcall/warrior/views.py:175
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/warrior/views.py:175 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `warrior_progress` may be unauthenticated — rollcall/warrior/views.py:254
Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.
rollcall/warrior/views.py:254 securityAuth django unauth view
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for att in …` triggers a query per row — rollcall/management/commands/generate_substack_ode.py:185
The loop iterates a Django queryset and accesses `att.user_mapping.linked_name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
rollcall/management/commands/generate_substack_ode.py:185 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for att in …` triggers a query per row — rollcall/management/commands/run_ranking_trial.py:1011
The loop iterates a Django queryset and accesses `att.parent_attestation.id` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 qu…
rollcall/management/commands/run_ranking_trial.py:1011 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for att in …` triggers a query per row — rollcall/views.py:572
The loop iterates a Django queryset and accesses `att.discord_user.linked_name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
rollcall/views.py:572 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for att in …` triggers a query per row — rollcall/warrior/views.py:303
The loop iterates a Django queryset and accesses `att.weekly_roll_call.week_start_date` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everythin…
rollcall/warrior/views.py:303 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for attestation in …` triggers a query per row — rollcall/bot_commands/status.py:76
The loop iterates a Django queryset and accesses `attestation.discord_user.discord_username` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load ever…
rollcall/bot_commands/status.py:76 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for dm in …` triggers a query per row — rollcall/management/commands/list_user_mappings.py:112
The loop iterates a Django queryset and accesses `dm.linked_twitter_handle.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1…
rollcall/management/commands/list_user_mappings.py:112 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for dm in …` triggers a query per row — rollcall/management/commands/list_user_mappings.py:155
The loop iterates a Django queryset and accesses `dm.linked_name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries…
rollcall/management/commands/list_user_mappings.py:155 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for em in …` triggers a query per row — rollcall/management/commands/bot_query.py:142
The loop iterates a Django queryset and accesses `em.attestation.weekly_roll_call` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in …
rollcall/management/commands/bot_query.py:142 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for model in …` triggers a query per row — rollcall/migrations/0003_chatcontextreset_and_more.py:39
The loop iterates a Django queryset and accesses `model.objects.filter` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries…
rollcall/migrations/0003_chatcontextreset_and_more.py:39 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for msg in …` triggers a query per row — discord_dashboard/bot/discord_bot.py:96
The loop iterates a Django queryset and accesses `msg.author.display_name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 quer…
discord_dashboard/bot/discord_bot.py:96 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for r in …` triggers a query per row — rollcall/views.py:149
The loop iterates a Django queryset and accesses `r.weekly_roll_call.week_start_date` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything …
rollcall/views.py:149 N plus onePerformance
medium System graph quality Integrity conf 1.00 2 occurrences Likely N+1 query: `for ranking in …` triggers a query per row — rollcall/discord_bot/cogs/ranking.py:114
The loop iterates a Django queryset and accesses `ranking.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries i…
lines 114
rollcall/discord_bot/cogs/ranking.py:114 (2 hits)
N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for ranking in …` triggers a query per row — rollcall/management/commands/generate_twitter_rankings.py:122
The loop iterates a Django queryset and accesses `ranking.twitter_handle.strip` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2…
rollcall/management/commands/generate_twitter_rankings.py:122 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for ranking in …` triggers a query per row — rollcall/management/commands/list_user_mappings.py:128
The loop iterates a Django queryset and accesses `ranking.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries i…
rollcall/management/commands/list_user_mappings.py:128 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for ranking in …` triggers a query per row — rollcall/management/commands/post_rankings_to_discord.py:241
The loop iterates a Django queryset and accesses `ranking.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries i…
rollcall/management/commands/post_rankings_to_discord.py:241 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for roll_call in …` triggers a query per row — rollcall/management/commands/post_rankings_to_discord.py:159
The loop iterates a Django queryset and accesses `roll_call.week_start_date.strftime` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything …
rollcall/management/commands/post_rankings_to_discord.py:159 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for tm in …` triggers a query per row — rollcall/management/commands/list_user_mappings.py:118
The loop iterates a Django queryset and accesses `tm.linked_twitter_handle.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1…
rollcall/management/commands/list_user_mappings.py:118 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for tm in …` triggers a query per row — rollcall/management/commands/list_user_mappings.py:162
The loop iterates a Django queryset and accesses `tm.linked_name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries…
rollcall/management/commands/list_user_mappings.py:162 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for trans in …` triggers a query per row — discord_dashboard/bot/discord_bot.py:317
The loop iterates a Django queryset and accesses `trans.user.display_name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 quer…
discord_dashboard/bot/discord_bot.py:317 N plus onePerformance
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 17 placeholder/mock markers across 8 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 7 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BOT_QUERY_MODE`, `BOT_SCOPE`, `TRANSCRIPTION_CHUNK_DURATION`, `USE_POSTGRESQL`, `VIEWER_TELEGRAM_ID`, `VOICE_TRANSCRIPTION_ENABLED`, `WHISPER_MODEL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Tests conf 1.00 Low test-to-source ratio
13 tests / 124 src (ratio 0.10).
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: discord_dashboard/bot/discord_bot.py:update_session, discord_dashboard/bot/discord_bot.py:update_session 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 th…
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: discord_dashboard/bot/management/commands/runbot.py:handle, discord_dashboard/bot/management/commands/backfill_messages.py:handle, rollcall/management/commands/run_discord_bot.py:handle, rollcall/management/commands/assign_top_ten_role.py:handle This…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `api_v1` in rollcall/management/commands/post_rankings_to_x.py:216
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: clear_daily_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
daily/auth.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: create_transcription
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
discord_dashboard/bot/discord_bot.py:274
low System graph software Dead code conf 1.00 Possibly dead Python function: db_for_read
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
rollcall/db_routers.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: db_for_write
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
rollcall/db_routers.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: derive_stretch_item
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
daily/services/ai_coach.py:225
low System graph software Dead code conf 1.00 Possibly dead Python function: update_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
discord_dashboard/bot/discord_bot.py:327
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: ANY /
`discord_dashboard/discord_intelligence/urls.py` declares `ANY /` 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: ANY /account/
`rollcall/urls.py` declares `ANY /account/` 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: ANY /account/link-discord/
`rollcall/urls.py` declares `ANY /account/link-discord/` 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: ANY /account/link-telegram/
`rollcall/urls.py` declares `ANY /account/link-telegram/` 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: ANY /account/unlink-discord/
`rollcall/urls.py` declares `ANY /account/unlink-discord/` 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: ANY /account/unlink-telegram/
`rollcall/urls.py` declares `ANY /account/unlink-telegram/` 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: ANY /admin/
`discord_dashboard/discord_intelligence/urls.py` declares `ANY /admin/` 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: ANY /api/messages/
`discord_dashboard/dashboard/urls.py` declares `ANY /api/messages/` 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: ANY /api/stats/
`discord_dashboard/dashboard/urls.py` declares `ANY /api/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: ANY /daily/
`strongasan0x/urls.py` declares `ANY /daily/` 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: ANY /daily/baseline/
`daily/urls.py` declares `ANY /daily/baseline/` 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: ANY /daily/bonus/next/
`daily/urls.py` declares `ANY /daily/bonus/next/` 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: ANY /daily/c/<uuid:token>/
`daily/urls.py` declares `ANY /daily/c/<uuid: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: ANY /daily/checkin/
`daily/urls.py` declares `ANY /daily/checkin/` 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: ANY /daily/comment/
`daily/urls.py` declares `ANY /daily/comment/` 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: ANY /daily/item/
`daily/urls.py` declares `ANY /daily/item/` 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: ANY /daily/suggestion/<int:suggestion_id>/respond/
`daily/urls.py` declares `ANY /daily/suggestion/<int:suggestion_id>/respond/` 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: ANY /daily/wrap/
`daily/urls.py` declares `ANY /daily/wrap/` 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: ANY /login/
`rollcall/urls.py` declares `ANY /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: ANY /logout/
`rollcall/urls.py` declares `ANY /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: ANY /review-attestations/
`rollcall/urls.py` declares `ANY /review-attestations/` 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: ANY /review-attestations/add/
`rollcall/urls.py` declares `ANY /review-attestations/add/` 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: ANY /review-attestations/toggle-hidden/<int:attestation_id>/
`rollcall/urls.py` declares `ANY /review-attestations/toggle-hidden/<int:attestation_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /telegram/webhook/
`rollcall/urls.py` declares `ANY /telegram/webhook/` 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: ANY /warrior/
`rollcall/urls.py` declares `ANY /warrior/` 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: ANY /warrior/callback/
`rollcall/warrior/urls.py` declares `ANY /warrior/callback/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /warrior/check-login/
`rollcall/warrior/urls.py` declares `ANY /warrior/check-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: ANY /warrior/dashboard/
`rollcall/warrior/urls.py` declares `ANY /warrior/dashboard/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /warrior/edit/
`rollcall/warrior/urls.py` declares `ANY /warrior/edit/` 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: ANY /warrior/history/
`rollcall/warrior/urls.py` declares `ANY /warrior/history/` 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: ANY /warrior/login/
`rollcall/warrior/urls.py` declares `ANY /warrior/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: ANY /warrior/logout/
`rollcall/warrior/urls.py` declares `ANY /warrior/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: ANY /warrior/progress/
`rollcall/warrior/urls.py` declares `ANY /warrior/progress/` 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: ANY /warrior/strava/attestation/
`rollcall/warrior/urls.py` declares `ANY /warrior/strava/attestation/` 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: ANY /warrior/strava/callback/
`rollcall/warrior/urls.py` declares `ANY /warrior/strava/callback/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /warrior/strava/link/
`rollcall/warrior/urls.py` declares `ANY /warrior/strava/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: ANY /warrior/strava/unlink/
`rollcall/warrior/urls.py` declares `ANY /warrior/strava/unlink/` 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: rollcall/management/commands/run_ranking_trial.py (1204 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/bc4a4cf7-ae25-46d6-97dd-1f41c5abd2a6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/bc4a4cf7-ae25-46d6-97dd-1f41c5abd2a6/

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.