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

Sue-Ann-CliniContact/cc_bridge

https://github.com/Sue-Ann-CliniContact/cc_bridge · scanned 2026-06-16 00:24 UTC (2 months, 2 weeks ago)

130 raw signals (0 security + 130 graph)

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

Complete repo analysis

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

JSON
Combined
64.6
/100
Security checks
65
0 findings
System graph
65
88.9% cov · 126 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 37 Low 69 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 126 Crowd 0 Layer: Software 4 Frontend 1 Security 15 Cicd 1 Quality 55 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 64.6/100 with 88.9% coverage. It contains 993 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 130 findings — concentrated in quality (59), api (50), security (15). Risk profile is low: 0 critical, 0 high, 37 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 106 of 126 actionable findings. 130 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/launch.json
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/launch.json VerificationClaude instruction
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, ci, tests, operator-readme. 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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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 auth conf 1.00 Django view `healthz` may be unauthenticated — accounts/views.py:45
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`.
accounts/views.py:45 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `invite_accept` may be unauthenticated — accounts/views.py:183
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`.
accounts/views.py:183 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `monday_callback` may be unauthenticated — accounts/views.py:89
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`.
accounts/views.py:89 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify_create_mapping` may be unauthenticated — partners/views.py:955
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`.
partners/views.py:955 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify_delete_mapping` may be unauthenticated — partners/views.py:1149
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`.
partners/views.py:1149 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify_hard_reset` may be unauthenticated — partners/views.py:1110
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`.
partners/views.py:1110 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify_recompute_counters` may be unauthenticated — partners/views.py:1087
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`.
partners/views.py:1087 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify_set_project` may be unauthenticated — partners/views.py:940
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`.
partners/views.py:940 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_dripify` may be unauthenticated — partners/views.py:823
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`.
partners/views.py:823 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_partner_resolve` may be unauthenticated — partners/views.py:770
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`.
partners/views.py:770 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `operator_partners` may be unauthenticated — partners/views.py:710
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`.
partners/views.py:710 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `partner_landing` may be unauthenticated — partners/views.py:155
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`.
partners/views.py:155 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `partner_verify` may be unauthenticated — partners/views.py:426
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`.
partners/views.py:426 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `staff_invite_accept` may be unauthenticated — accounts/views.py:256
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`.
accounts/views.py:256 securityAuth django unauth view
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/webflow_bridge_landing.html:29
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/webflow_bridge_landing.html:29 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for b in …` triggers a query per row — core/views.py:4919
The loop iterates a Django queryset and accesses `b.project_lead.campaign` 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…
core/views.py:4919 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for campaign in …` triggers a query per row — core/management/commands/sync_instantly.py:80
The loop iterates a Django queryset and accesses `campaign.project.study_code` 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 …
core/management/commands/sync_instantly.py:80 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for ev in …` triggers a query per row — core/views.py:2122
The loop iterates a Django queryset and accesses `ev.project_lead.lead_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 quer…
core/views.py:2122 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for ev in …` triggers a query per row — core/views.py:4894
The loop iterates a Django queryset and accesses `ev.project_lead.lead_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 quer…
core/views.py:4894 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for event in …` triggers a query per row — core/services/client_portal.py:145
The loop iterates a Django queryset and accesses `event.timestamp.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 in 1-2 queries…
core/services/client_portal.py:145 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for lead in …` triggers a query per row — core/views.py:1543
The loop iterates a Django queryset and accesses `lead.email_history.all` 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 queri…
core/views.py:1543 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for lead in …` triggers a query per row — core/views.py:1561
The loop iterates a Django queryset and accesses `lead.project_lead.latest_reply_event` 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…
core/views.py:1561 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for org in …` triggers a query per row — core/migrations/0028_rekey_partner_organizations.py:231
The loop iterates a Django queryset and accesses `org.leads.values_list` 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 querie…
core/migrations/0028_rekey_partner_organizations.py:231 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for partner in …` triggers a query per row — core/services/client_portal.py:1255
The loop iterates a Django queryset and accesses `partner.lead.organization` 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…
core/services/client_portal.py:1255 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/management/commands/sync_instantly.py:207
The loop iterates a Django queryset and accesses `pl.lead.email` 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 instea…
core/management/commands/sync_instantly.py:207 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/management/commands/sync_instantly.py:211
The loop iterates a Django queryset and accesses `pl.lead.email_history` 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 querie…
core/management/commands/sync_instantly.py:211 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/views.py:2222
The loop iterates a Django queryset and accesses `pl.lead.organization_obj` 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 que…
core/views.py:2222 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/views.py:4702
The loop iterates a Django queryset and accesses `pl.lead.geography` 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 in…
core/views.py:4702 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/views.py:5939
The loop iterates a Django queryset and accesses `pl.lead.email` 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 instea…
core/views.py:5939 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pl in …` triggers a query per row — core/views.py:5943
The loop iterates a Django queryset and accesses `pl.lead.email_history` 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 querie…
core/views.py:5943 N plus onePerformance
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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 59 placeholder/mock markers across 9 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
2 test file(s) for 97 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 18 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AI_DEFAULT_PROVIDER`, `BRIDGE_OUTREACH_GMAIL_FROM`, `BRIDGE_PERMANENT_SUPERUSER_EMAILS`, `CSRF_TRUSTED_ORIGINS`, `DEEPSEEK_API_KEY`, `DEEPSEEK_DEFAULT_MODEL`, `DEEPSEEK_MAX_OUTPUT_TOKENS`, `DEFAULT_FROM_EMAIL` + 10 more. Add them (with a placehold…
config drift
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: ai_manager/services.py:call_structured_with_web_search, ai_manager/services.py:call_structured 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 sepa…
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Docs conf 1.00 No README detected
No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.
ReadmeRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_search_legacy` in integrations/hrsa.py:137
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 `webhook_dripify_legacy` in partners/urls.py:74
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 `webhook_dripify_legacy` in partners/views.py:1274
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: as_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/services/sourcing.py:150
low System graph software Dead code conf 1.00 Possibly dead Python function: clear_cache
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
integrations/census.py:102
low System graph software Dead code conf 1.00 Possibly dead Python function: discover_people
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
integrations/apollo.py:250
low System graph software Dead code conf 1.00 Possibly dead Python function: search_multi
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
integrations/npi.py:102
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 /
`accounts/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 /api/projects/<int:project_id>/leads/<int:lead_id>/remove/
`core/urls.py` declares `ANY /api/projects/<int:project_id>/leads/<int:lead_id>/remove/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/webhooks/dripify/
`partners/urls.py` declares `ANY /api/webhooks/dripify/` 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/webhooks/dripify/<str:secret>/
`partners/urls.py` declares `ANY /api/webhooks/dripify/<str:secret>/` 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/webhooks/dripify/<str:secret>/m/<str:slug>/
`partners/urls.py` declares `ANY /api/webhooks/dripify/<str:secret>/m/<str: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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /bridge/staff/invite/
`core/urls.py` declares `ANY /bridge/staff/invite/` 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 /bridge/staff/invites/<int:invite_id>/revoke/
`core/urls.py` declares `ANY /bridge/staff/invites/<int:invite_id>/revoke/` 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 /dashboard/
`core/urls.py` declares `ANY /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 /dashboard/ai/
`core/urls.py` declares `ANY /dashboard/ai/` 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 /invite/<str:token>/
`accounts/urls.py` declares `ANY /invite/<str: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 /logout/
`accounts/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 /oauth/callback/
`accounts/urls.py` declares `ANY /oauth/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 /oauth/login/
`accounts/urls.py` declares `ANY /oauth/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 /orgs/
`core/urls.py` declares `ANY /orgs/` 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 /orgs/<int:org_id>/
`core/urls.py` declares `ANY /orgs/<int:org_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: ANY /orgs/<int:org_id>/domain/
`core/urls.py` declares `ANY /orgs/<int:org_id>/domain/` 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 /orgs/<int:org_id>/domain/recompute/
`core/urls.py` declares `ANY /orgs/<int:org_id>/domain/recompute/` 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 /orgs/<int:org_id>/notes/
`core/urls.py` declares `ANY /orgs/<int:org_id>/notes/` 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 /orgs/<int:org_id>/recompute/
`core/urls.py` declares `ANY /orgs/<int:org_id>/recompute/` 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 /orgs/<int:org_id>/state/
`core/urls.py` declares `ANY /orgs/<int:org_id>/state/` 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 /partners/
`partners/urls.py` declares `ANY /partners/` 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 /partners/admin/
`partners/urls.py` declares `ANY /partners/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 /partners/admin/<int:partner_id>/resolve/
`partners/urls.py` declares `ANY /partners/admin/<int:partner_id>/resolve/` 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 /partners/admin/dripify/
`partners/urls.py` declares `ANY /partners/admin/dripify/` 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 /partners/admin/dripify/<int:mapping_id>/delete/
`partners/urls.py` declares `ANY /partners/admin/dripify/<int:mapping_id>/delete/` 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: ANY /partners/admin/dripify/<int:mapping_id>/set-project/
`partners/urls.py` declares `ANY /partners/admin/dripify/<int:mapping_id>/set-project/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /partners/admin/dripify/create/
`partners/urls.py` declares `ANY /partners/admin/dripify/create/` 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 /partners/admin/dripify/hard-reset/
`partners/urls.py` declares `ANY /partners/admin/dripify/hard-reset/` 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 /partners/admin/dripify/recompute-counters/
`partners/urls.py` declares `ANY /partners/admin/dripify/recompute-counters/` 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 /partners/admin/dripify/wipe-test-data/
`partners/urls.py` declares `ANY /partners/admin/dripify/wipe-test-data/` 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 /partners/dashboard/
`partners/urls.py` declares `ANY /partners/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 /partners/login/
`partners/urls.py` declares `ANY /partners/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 /partners/logout/
`partners/urls.py` declares `ANY /partners/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 /partners/register/
`partners/urls.py` declares `ANY /partners/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: ANY /partners/studies/<str:study_code>/
`partners/urls.py` declares `ANY /partners/studies/<str:study_code>/` 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 /partners/studies/<str:study_code>/refer/
`partners/urls.py` declares `ANY /partners/studies/<str:study_code>/refer/` 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 /partners/verify/<str:token>/
`partners/urls.py` declares `ANY /partners/verify/<str: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 /portal/
`core/urls.py` declares `ANY /portal/` 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 /portal/ai/
`core/urls.py` declares `ANY /portal/ai/` 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 /portal/projects/<int:project_id>/
`core/urls.py` declares `ANY /portal/projects/<int:project_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: ANY /portal/projects/<int:project_id>/ai/
`core/urls.py` declares `ANY /portal/projects/<int:project_id>/ai/` 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 /project-leads/<int:project_lead_id>/log-interaction/
`core/urls.py` declares `ANY /project-leads/<int:project_lead_id>/log-interaction/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /projects/<int:project_id>/
`core/urls.py` declares `ANY /projects/<int:project_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: ANY /projects/<int:project_id>/ai/
`core/urls.py` declares `ANY /projects/<int:project_id>/ai/` 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 /projects/<int:project_id>/assets/
`core/urls.py` declares `ANY /projects/<int:project_id>/assets/` 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 /projects/<int:project_id>/cleanup/
`core/urls.py` declares `ANY /projects/<int:project_id>/cleanup/` 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 /projects/<int:project_id>/cleanup/action/
`core/urls.py` declares `ANY /projects/<int:project_id>/cleanup/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: ANY /projects/<int:project_id>/orgs/<int:org_id>/sourcing/
`core/urls.py` declares `ANY /projects/<int:project_id>/orgs/<int:org_id>/sourcing/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /projects/new/
`core/urls.py` declares `ANY /projects/new/` 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 /staff-invite/<str:token>/
`accounts/urls.py` declares `ANY /staff-invite/<str: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 quality Complexity conf 1.00 Very large file: core/models.py (1264 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/services/client_portal.py (3154 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/services/sourcing.py (3127 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: core/views.py (8054 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integrations/ai_sourcing.py (2252 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: integrations/instantly.py (1331 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: partners/views.py (1282 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/1cd9803c-e005-44e1-8a0f-c243bb7521b5/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1cd9803c-e005-44e1-8a0f-c243bb7521b5/

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.