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
35 of your 102 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 98.59s for a 104.4 MB repo slow.
  • Repobility's analysis ran in 12.55s after the clone landed.

Shopify/polaris-react

https://github.com/Shopify/polaris-react.git · scanned 2026-05-24 01:23 UTC (2 weeks, 6 days ago) · 10 languages

1326 raw signals (89 security + 1237 graph) 11/13 scanners ran 87th percentile · Typescript · large (100-500K LoC) System graph score 76 (higher by 9)

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

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v4 · last Δ -5.4 (diff) · 235 actionable findings from 3 signal sources. 70 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
79.1
/100
Security checks
82
35 findings
System graph
76
100.0% cov · 199 findings
Critical
4
click to filter
Agents
6
3 votes
Crowd
1
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 95.0 0.20 19.00
documentation_score 61.0 0.15 9.15
practices_score 100.0 0.15 15.00
code_quality 80.0 0.10 8.00
Overall 1.00 85.2
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 4 High 6 Medium 58 Low 108 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 35 System graph 199 Crowd 1 Layer: Software 22 Quality 101 Security 58 Cicd 3 Frontend 1 Api 50
Scan summary Quality grade A- (85/100). Dimensions: security 100, maintainability 60. 89 findings (14 security). 195,463 lines analyzed.

Showing 174 of 235 actionable findings. 305 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.

low Security checks cicd CI/CD security conf 0.35 ✓ Repobility Workflow references repository secrets in a pull_request workflow
Fork pull_request runs do not receive normal repository secrets on GitHub Actions. Review this as a reliability/intent signal, not as direct fork-secret exfiltration. Raise severity only for pull_request_target or another trusted-context path that runs untrusted PR code with secrets.
.github/workflows/ci-a11y-vrt.yml:166 CI/CD securityworkflow secretsGitHub Actions
critical System graph security Secrets conf 1.00 Possible secret in repos/monitoring_tasks.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
repos/monitoring_tasks.py:269
critical System graph security Secrets conf 1.00 Possible secret in repos/threat_engine.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
repos/threat_engine.py:110
critical System graph security Secrets conf 1.00 Possible secret in scanner/engine/ai/client.py
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
scanner/engine/ai/client.py:106
medium Security checks cicd CI/CD security conf 0.90 ✓ Repobility 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
[MINED115] Action `Shopify/shopify-cla-action` pinned to mutable ref `@v1`: `uses: Shopify/shopify-cla-action@v1` resolves at workflow-run time. Tags and branches can be re-pushed by the action owner; that made the tj-actions/changed-files compromise (2025) instantly affect ~23K repos. Pin to a 40-…
2 files, 2 locations
.github/workflows/cla.yml:19
.github/workflows/snapit.yml:22
CI/CD securitySupply chainGitHub Actions
high System graph security security conf 1.00 Insecure pattern 'eval_used' in repos/supply_chain_scanner.py:323
Found a known-risky pattern (eval_used). Review and replace if possible.
repos/supply_chain_scanner.py:323 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in repos/threat_engine.py:1732
Found a known-risky pattern (eval_used). Review and replace if possible.
repos/threat_engine.py:1732 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in repos/supply_chain_scanner.py:323
Found a known-risky pattern (exec_used). Review and replace if possible.
repos/supply_chain_scanner.py:323 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in repos/threat_engine.py:1732
Found a known-risky pattern (exec_used). Review and replace if possible.
repos/threat_engine.py:1732 Exec used
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in repos/threat_engine.py:3682
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
repos/threat_engine.py:3682 Tls verify false
medium Security checks security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.
Add .repobility/access.yml mapping routes to anonymous, authenticated, owner, admin, and super_admin. Keep business-specific rules in the repo so CI can enforce them.
medium Security checks quality Error handling conf 1.00 [ERR002] Empty Catch Block: Empty catch blocks hide errors.
Log the error or rethrow it. Use console.error() at minimum.
polaris.shopify.com/pages/_app.tsx:30
low Security checks security Deserialization conf 1.00 3 occurrences [SEC007] Unsafe Deserialization: Unsafe deserialization can execute arbitrary code.
Use yaml.safe_load() instead of yaml.load(). Avoid pickle for untrusted data.
3 files, 3 locations
.eslintrc.js:6
polaris-icons/rollup.config.mjs:28
polaris.shopify.com/src/utils/markdown.mjs:9
medium Security checks software Open redirect conf 1.00 [SEC046] Client-side open redirect — window.location = server-supplied URL: Assigning window.location from a server-supplied URL trusts the server endpoint to never return a hostile destination. If that endpoint is ever subverted (compromised admin, JSON injection, MITM on a webhook), users get redirected to a phishing site they trust because the original page is yours. CWE-601 (server-side OR client-side). Complement to server-side SEC030.
Validate the URL is same-origin or on an explicit allowlist before assignment: const u = new URL(serverUrl, location.href); if (u.origin !== location.origin && !ALLOWED.includes(u.host)) return; location.assign(u); Even better: have the server return a path (/checkout/done) instead of a full …
polaris.shopify.com/src/components/InterstitialModal/InterstitialModal.tsx:199
low Security checks quality Quality conf 1.00 [SEC136] AI-typical over-broad exception handler swallowing all errors: Catch-all exception block that silently returns success or no-ops. AI agents reach for this pattern when a flaky test or an unfamiliar API throws — wrap, swallow, return success. Real bugs are masked, observability is destroyed, and callers think the operation worked. CWE-396 (improperly-generalized exception). Distinct from intentional fallback because there's no log line and the success value is fabricated.
Catch the specific exception type, log at error level with full exception info, and return a failure-shaped result. If the operation is genuinely best-effort, log at warning and document why in a comment so the next reader (or scanner) knows.
polaris.shopify.com/playroom/FrameComponent.tsx:44
medium System graph security auth conf 1.00 Django view `ai_audit_landing` may be unauthenticated — landing/views.py:216
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`.
landing/views.py:216 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_cve_feed` may be unauthenticated — repos/alert_views.py:88
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`.
repos/alert_views.py:88 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_stats` may be unauthenticated — repos/roast_views.py:186
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`.
repos/roast_views.py:186 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_webhook_deliveries` may be unauthenticated — repos/webhook_views.py:64
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`.
repos/webhook_views.py:64 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_webhooks` may be unauthenticated — repos/webhook_views.py:53
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`.
repos/webhook_views.py:53 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `badge_svg` may be unauthenticated — repos/roast_views.py:127
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`.
repos/roast_views.py:127 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `blog_category` may be unauthenticated — blog/views.py:82
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`.
blog/views.py:82 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `blog_post` may be unauthenticated — blog/views.py:55
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`.
blog/views.py:55 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `changelog` may be unauthenticated — landing/views.py:210
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`.
landing/views.py:210 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `cors_preflight` may be unauthenticated — repos/unified_views.py:2236
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`.
repos/unified_views.py:2236 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `cve_feed` may be unauthenticated — repos/alert_views.py:57
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`.
repos/alert_views.py:57 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `dataset_detail` may be unauthenticated — blog/views.py:141
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`.
blog/views.py:141 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `docs` may be unauthenticated — landing/views.py:190
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`.
landing/views.py:190 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `features` may be unauthenticated — landing/views.py:182
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`.
landing/views.py:182 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `file_issue_preview` may be unauthenticated — repos/file_issue/views.py:119
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`.
repos/file_issue/views.py:119 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `humans_txt` may be unauthenticated — landing/views.py:370
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`.
landing/views.py:370 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `install_callback` may be unauthenticated — repos/github_app/views.py:48
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`.
repos/github_app/views.py:48 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `install_page` may be unauthenticated — repos/github_app/views.py:39
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`.
repos/github_app/views.py:39 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `integrate_page` may be unauthenticated — landing/views.py:396
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`.
landing/views.py:396 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `llms_txt` may be unauthenticated — landing/views.py:293
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`.
landing/views.py:293 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `pricing` may be unauthenticated — landing/views.py:176
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`.
landing/views.py:176 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `privacy_policy` may be unauthenticated — landing/views.py:198
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`.
landing/views.py:198 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `quality_badge` may be unauthenticated — repos/badge_views.py:65
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`.
repos/badge_views.py:65 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `repobility_badge` may be unauthenticated — repos/badge_views.py:194
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`.
repos/badge_views.py:194 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `roast_api_status` may be unauthenticated — repos/roast_views.py:60
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`.
repos/roast_views.py:60 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `roast_page` may be unauthenticated — repos/roast_views.py:25
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`.
repos/roast_views.py:25 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `roast_result_page` may be unauthenticated — repos/roast_views.py:68
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`.
repos/roast_views.py:68 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `scan_detail_v2_json` may be unauthenticated — rp/views.py:69
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`.
rp/views.py:69 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `scan_detail_v2` may be unauthenticated — rp/views.py:19
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`.
rp/views.py:19 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `security_badge` may be unauthenticated — repos/badge_views.py:102
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`.
repos/badge_views.py:102 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `security_page` may be unauthenticated — landing/views.py:206
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`.
landing/views.py:206 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `security_txt` may be unauthenticated — landing/views.py:358
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`.
landing/views.py:358 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `service_api_key` may be unauthenticated — repos/api_views.py:80
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`.
repos/api_views.py:80 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `terms_of_service` may be unauthenticated — landing/views.py:202
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`.
landing/views.py:202 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `trend_ingest` may be unauthenticated — repos/trend_views.py:12
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`.
repos/trend_views.py:12 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `trend_list` may be unauthenticated — repos/trend_views.py:8
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`.
repos/trend_views.py:8 securityAuth django unauth view
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in repos/threat_engine.py:2475
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
repos/threat_engine.py:2475 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in repos/threat_engine.py:4164
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
repos/threat_engine.py:4164 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in repos/threat_engine.py:3902
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
repos/threat_engine.py:3902 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in repos/threat_engine.py:3570
Found a known-risky pattern (weak_hash). Review and replace if possible.
repos/threat_engine.py:3570 Weak hash
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for a in …` triggers a query per row — repos/unified.py:762
The loop iterates a Django queryset and accesses `a.registered_at.isoformat` 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…
repos/unified.py:762 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for cr in …` triggers a query per row — repos/unified.py:796
The loop iterates a Django queryset and accesses `cr.created_at.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 in 1-2 queri…
repos/unified.py:796 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for fb in …` triggers a query per row — repos/unified.py:344
The loop iterates a Django queryset and accesses `fb.created_at.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 in 1-2 queri…
repos/unified.py:344 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for fb in …` triggers a query per row — repos/unified.py:778
The loop iterates a Django queryset and accesses `fb.created_at.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 in 1-2 queri…
repos/unified.py:778 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for fi in …` triggers a query per row — repos/monitoring_tasks.py:1355
The loop iterates a Django queryset and accesses `fi.repo_full_name.partition` 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 …
repos/monitoring_tasks.py:1355 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for fi in …` triggers a query per row — repos/unified_views.py:2890
The loop iterates a Django queryset and accesses `fi.filed_at.isoformat` 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…
repos/unified_views.py:2890 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for r in …` triggers a query per row — scanner/templatetags/scanner_panel.py:155
The loop iterates a Django queryset and accesses `r.languages.get` 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 inst…
scanner/templatetags/scanner_panel.py:155 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for rc in …` triggers a query per row — repos/unified_views.py:1866
The loop iterates a Django queryset and accesses `rc.last_updated_at.isoformat` 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…
repos/unified_views.py:1866 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for repo in …` triggers a query per row — repos/management/commands/backfill_remediation_tasks.py:22
The loop iterates a Django queryset and accesses `repo.findings.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…
repos/management/commands/backfill_remediation_tasks.py:22 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for repo in …` triggers a query per row — repos/management/commands/cleanup_duplicate_structural_findings.py:33
The loop iterates a Django queryset and accesses `repo.findings.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…
repos/management/commands/cleanup_duplicate_structural_findings.py:33 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for repo in …` triggers a query per row — repos/monitoring_tasks.py:1555
The loop iterates a Django queryset and accesses `repo.full_name.partition` 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…
repos/monitoring_tasks.py:1555 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for s in …` triggers a query per row — repos/unified_views.py:3787
The loop iterates a Django queryset and accesses `s.taken_at.isoformat` 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…
repos/unified_views.py:3787 N plus onePerformance
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — repos/monitoring_tasks.py:295
`requests.get(...)` 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 Integrity conf 1.00 Network/subprocess call without timeout or try/except — repos/threat_engine.py:4661
`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
low Security checks security auth conf 0.76 [AUC005] No authorization-focused tests detected: No test files with common authorization, ownership, 403, admin, or super_admin assertions were found.
Add regression tests for anonymous denial, cross-user object denial, admin role limits, and super_admin-only behavior.
low Security checks quality Quality conf 0.60 26 occurrences Duplicated implementation block across source files
Duplicate implementation blocks are maintenance debt. Keep them visible, but they are not a high-severity defect unless the duplicated logic is security-sensitive or drifting.
12 files, 16 locations
polaris-react/src/components/BulkActions/components/BulkActionsMeasurer/BulkActionsMeasurer.tsx:32, 61 (2 hits)
polaris-react/src/components/Sheet/Sheet.stories.tsx:166, 322 (2 hits)
polaris-react/src/components/Tabs/components/Tab/components/RenameModal/RenameModal.tsx:48, 100 (2 hits)
polaris-react/src/components/VideoThumbnail/VideoThumbnail.stories.tsx:7, 34 (2 hits)
polaris-migrator/jest.config.js:1
polaris-react/src/components/ColorPicker/components/HuePicker/HuePicker.tsx:15
polaris-react/src/components/Combobox/Combobox.stories.tsx:17
polaris-react/src/components/LegacyCard/LegacyCard.stories.tsx:373
duplicationquality
low System graph software Dead code candidate conf 1.00 File has no detected symbols: blog/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: dashboard/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: landing/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/celery.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/settings.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/settings_dev.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/settings_test.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repobility/wsgi.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repos/api_urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repos/confidence.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repos/scoring_config.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: repos/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: rp/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph software Dead code candidate conf 1.00 File has no detected symbols: scanner/urls.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 16, 36
.github/workflows/ci.yml:16, 36 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
31 tests / 250 src (ratio 0.12).
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: repos/tasks.py:mark_repository_analysis_failed, repos/tasks.py:mark_repository_not_scannable 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 separa…
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: repos/api_views.py:perform_create, repos/api_views.py:perform_create, repos/api_views.py:perform_create 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 the…
3 occurrences
repo-level (3 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: repos/serializers.py:update, repos/serializers.py:update, repos/serializers.py:update, repos/serializers.py:update This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: repos/views.py:repo_task_update, repos/views.py:repo_finding_triage, repos/views.py:repo_automation_update, repos/views.py:repo_heartbeat_now This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hyg…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: repos/sitemaps.py:items, repos/sitemaps.py:items, repos/sitemaps.py:items, repos/sitemaps.py:items 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 …
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: repos/corpus_admin.py:has_add_permission, repos/corpus_admin.py:has_add_permission, repos/corpus_admin.py:has_add_permission, repos/corpus_admin.py:has_add_permission This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see …
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_from_legacy` in repos/rp_read.py:62
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 `_queue_legacy` in repos/tasks.py:132
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 `_queue_legacy` in repos/unified_views.py:67
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 `action_queue_v1` in tests/test_agent_runtime_scanner.py:42
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 `broad_copy` in repos/docker_scanner.py:1005
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 `eslint_unused` in repos/ai_code_scanner.py:19
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 `file_issue_v1` in repos/file_issue/views.py:136
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 `get_user_old` in scanner/engine/analyzers/integrity.py:50
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 `home_stats_live_v2` in landing/corpus_intelligence_helpers.py:27
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 `imported_legacy` in rp/models.py:82
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 `r71_build_percentile_cache_v2` in repos/monitoring_tasks.py:2951
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 `scan_detail_v2` in rp/urls.py:2
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 `scan_detail_v2` in rp/views.py:19
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_repo_list_disambiguates_duplicate_names_and_uses_neutral_issue_copy` in tests/test_views.py:79
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 `use_copy` in repos/migrate_phase2.py:32
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 `wiring_unused` in repos/unified.py:133
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: is_actionable_raw_finding
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
repos/tracking.py:84
low System graph software Dead code conf 1.00 Possibly dead Python function: search_endpoints
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
repos/baseline.py:203
low System graph software Dead code conf 1.00 Possibly dead Python function: search_repos
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
repos/baseline.py:227
low System graph software Dead code conf 1.00 Possibly dead Python function: search_symbols
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
repos/baseline.py:178
low System graph api Wiring conf 1.00 Unused endpoint: ANY /alerts/read/<int:alert_id>/
`repos/alert_views.py` declares `ANY /alerts/read/<int:alert_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 /alerts/toggle/<int:repo_id>/
`repos/alert_views.py` declares `ANY /alerts/toggle/<int:repo_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 /api/v1/cve/
`repos/alert_views.py` declares `ANY /api/v1/cve/` 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/v1/webhooks/
`repos/webhook_views.py` declares `ANY /api/v1/webhooks/` 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/v1/webhooks/<int:webhook_id>/deliveries/
`repos/webhook_views.py` declares `ANY /api/v1/webhooks/<int:webhook_id>/deliveries/` 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 consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /badge/<str:owner>/<str:repo>/quality.svg
`repos/badge_views.py` declares `ANY /badge/<str:owner>/<str:repo>/quality.svg` 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 /badge/<str:owner>/<str:repo>/repobility.svg
`repos/badge_views.py` declares `ANY /badge/<str:owner>/<str:repo>/repobility.svg` 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 /badge/<str:owner>/<str:repo>/security.svg
`repos/badge_views.py` declares `ANY /badge/<str:owner>/<str:repo>/security.svg` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /dashboard/
`dashboard/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/alerts/
`repos/alert_views.py` declares `ANY /dashboard/alerts/` 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/findings/
`dashboard/urls.py` declares `ANY /dashboard/findings/` 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/settings/
`dashboard/urls.py` declares `ANY /dashboard/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: ANY /dashboard/webhooks/
`repos/webhook_views.py` declares `ANY /dashboard/webhooks/` 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/webhooks/<int:webhook_id>/
`repos/webhook_views.py` declares `ANY /dashboard/webhooks/<int:webhook_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 /intel/cve-feed/
`repos/alert_views.py` declares `ANY /intel/cve-feed/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /repos/
`repos/urls.py` declares `ANY /repos/` 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 /repos/<int:pk>/
`repos/urls.py` declares `ANY /repos/<int:pk>/` 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 /repos/<int:pk>/automation/
`repos/urls.py` declares `ANY /repos/<int:pk>/automation/` 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 /repos/<int:pk>/delete/
`repos/urls.py` declares `ANY /repos/<int:pk>/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 it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /repos/<int:pk>/findings/
`repos/urls.py` declares `ANY /repos/<int:pk>/findings/` 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 /repos/<int:pk>/findings/<int:finding_id>/triage/
`repos/urls.py` declares `ANY /repos/<int:pk>/findings/<int:finding_id>/triage/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /repos/<int:pk>/heartbeat/
`repos/urls.py` declares `ANY /repos/<int:pk>/heartbeat/` 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 /repos/<int:pk>/onboarding-pr/
`repos/urls.py` declares `ANY /repos/<int:pk>/onboarding-pr/` 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 /repos/<int:pk>/prompts/
`repos/urls.py` declares `ANY /repos/<int:pk>/prompts/` 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 /repos/<int:pk>/reanalyze/
`repos/urls.py` declares `ANY /repos/<int:pk>/reanalyze/` 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 /repos/<int:pk>/request-deep-scan/
`repos/urls.py` declares `ANY /repos/<int:pk>/request-deep-scan/` 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 /repos/<int:pk>/run-all/
`repos/urls.py` declares `ANY /repos/<int:pk>/run-all/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /repos/<int:pk>/sarif/
`repos/urls.py` declares `ANY /repos/<int:pk>/sarif/` 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 /repos/<int:pk>/tasks/<int:task_id>/update/
`repos/urls.py` declares `ANY /repos/<int:pk>/tasks/<int:task_id>/update/` 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 /repos/<int:pk>/toggle-share/
`repos/urls.py` declares `ANY /repos/<int:pk>/toggle-share/` 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 /repos/add/
`repos/urls.py` declares `ANY /repos/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 /repos/add/url/
`repos/urls.py` declares `ANY /repos/add/url/` 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 /repos/agents/voting/
`repos/urls.py` declares `ANY /repos/agents/voting/` 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 /repos/api/v1/agents/feedback/
`repos/urls.py` declares `ANY /repos/api/v1/agents/feedback/` 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 /repos/api/v1/agents/register/
`repos/urls.py` declares `ANY /repos/api/v1/agents/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 /repos/api/v1/agents/report/
`repos/urls.py` declares `ANY /repos/api/v1/agents/report/` 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 /repos/api/v1/cohort/
`repos/urls.py` declares `ANY /repos/api/v1/cohort/` 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 /repos/api/v1/corpus/stats/
`repos/urls.py` declares `ANY /repos/api/v1/corpus/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 /repos/api/v1/digest/
`repos/urls.py` declares `ANY /repos/api/v1/digest/` 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 /repos/api/v1/findings/<int:finding_id>/feedback/
`repos/urls.py` declares `ANY /repos/api/v1/findings/<int:finding_id>/feedback/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /repos/api/v1/findings/queue/
`repos/urls.py` declares `ANY /repos/api/v1/findings/queue/` 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 /repos/api/v1/findings/suggest/
`repos/urls.py` declares `ANY /repos/api/v1/findings/suggest/` 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 /repos/api/v1/public/alert-signup/
`repos/urls.py` declares `ANY /repos/api/v1/public/alert-signup/` 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 /repos/api/v1/public/scan/
`repos/urls.py` declares `ANY /repos/api/v1/public/scan/` 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 /repos/api/v1/public/scan/<str:share_token>/
`repos/urls.py` declares `ANY /repos/api/v1/public/scan/<str:share_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 /repos/api/v1/rule_calibration/
`repos/urls.py` declares `ANY /repos/api/v1/rule_calibration/` 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 /repos/automation/sweep/
`repos/urls.py` declares `ANY /repos/automation/sweep/` 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 /repos/scan-submit/
`repos/urls.py` declares `ANY /repos/scan-submit/` 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 /repos/scan/<str:share_token>/
`repos/urls.py` declares `ANY /repos/scan/<str:share_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 /repos/scan/<str:share_token>/report.png
`repos/urls.py` declares `ANY /repos/scan/<str:share_token>/report.png` 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: blog/bulk_generators.py (2846 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/analyzer.py (2406 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/authz_dataset.py (1655 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/docker_scanner.py (1740 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/models.py (1315 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/monitoring_tasks.py (3025 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/supply_chain_scanner.py (1196 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/threat_engine.py (5673 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/unified_views.py (3867 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: repos/views.py (1427 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/35d5e407-be21-4f07-a11b-d74b3c497e35/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/35d5e407-be21-4f07-a11b-d74b3c497e35/

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.