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

salafan391-ai/car_aucttions_multi_site

https://github.com/salafan391-ai/car_aucttions_multi_site · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

141 raw signals (3 security + 138 graph)

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

Complete repo analysis

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

JSON
Combined
67.1
/100
Security checks
67
3 findings
System graph
67
100.0% cov · 125 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 1 Medium 50 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 125 Crowd 0 Layer: Quality 41 Software 2 Frontend 1 Security 33 Cicd 1 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 67.1/100 with 100.0% coverage. It contains 1494 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 138 findings — concentrated in quality (51), api (50), security (33). Risk profile is low: 0 critical, 0 high, 48 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

high Security checks quality Practices conf 0.84 3 occurrences Foundry mined bad chains: salafan391-ai/car_aucttions_multi_site
Comment chain pattern product: bad_chains Repo: salafan391-ai/car_aucttions_multi_site Thread: salafan391-ai/car_aucttions_multi_site#3 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source…
3 occurrences
repo-level (3 hits)
medium Security checks quality maintenance conf 0.70 Foundry mined blueprint gap alignment: salafan391-ai/car_aucttions_multi_site
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
medium Security checks quality Practices conf 0.70 3 occurrences Foundry mined unresolved feedback: salafan391-ai/car_aucttions_multi_site
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: assu…
3 occurrences
repo-level (3 hits)
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 `accessories_detail` may be unauthenticated — site_shop/views.py:117
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`.
site_shop/views.py:117 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `accessories_list` may be unauthenticated — site_shop/views.py:92
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`.
site_shop/views.py:92 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_badges_by_model` may be unauthenticated — cars/views.py:1671
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`.
cars/views.py:1671 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `api_models_by_manufacturer` may be unauthenticated — cars/views.py:1559
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`.
cars/views.py:1559 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_availability_check` may be unauthenticated — cars/views.py:3325
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`.
cars/views.py:3325 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_detail_by_pk` may be unauthenticated — cars/views.py:1767
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`.
cars/views.py:1767 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_detail` may be unauthenticated — cars/views.py:1872
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`.
cars/views.py:1872 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_list` may be unauthenticated — cars/views.py:832
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`.
cars/views.py:832 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_price_comparison` may be unauthenticated — cars/views.py:1967
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`.
cars/views.py:1967 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_report` may be unauthenticated — cars/views.py:2679
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`.
cars/views.py:2679 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `car_request` may be unauthenticated — cars/views.py:1987
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`.
cars/views.py:1987 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `expired_auctions` may be unauthenticated — cars/views.py:1522
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`.
cars/views.py:1522 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `export_auction_pdf` may be unauthenticated — cars/views.py:494
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`.
cars/views.py:494 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `faq` may be unauthenticated — site_cars/views.py:520
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`.
site_cars/views.py:520 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `landing` may be unauthenticated — cars/views.py:129
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`.
cars/views.py:129 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `manufacturer_logo` may be unauthenticated — cars/views.py:2470
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`.
cars/views.py:2470 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `page_view` may be unauthenticated — site_builder/views.py:41
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`.
site_builder/views.py:41 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `parts_detail` may be unauthenticated — site_shop/views.py:113
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`.
site_shop/views.py:113 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `parts_list` may be unauthenticated — site_shop/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`.
site_shop/views.py:88 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `pdf_export_delete` may be unauthenticated — cars/views.py:760
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`.
cars/views.py:760 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `pdf_export_panel` may be unauthenticated — cars/views.py:547
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`.
cars/views.py:547 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `post_detail` may be unauthenticated — cars/views.py:2219
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`.
cars/views.py:2219 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `post_list` may be unauthenticated — cars/views.py:2196
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`.
cars/views.py:2196 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `site_car_detail` may be unauthenticated — site_cars/views.py:393
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`.
site_cars/views.py:393 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `site_car_list` may be unauthenticated — site_cars/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`.
site_cars/views.py:82 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `sold_cars` may be unauthenticated — site_cars/views.py:400
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`.
site_cars/views.py:400 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `toggle_wishlist` may be unauthenticated — cars/views.py:2116
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`.
cars/views.py:2116 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `wishlist_count` may be unauthenticated — cars/views.py:2175
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`.
cars/views.py:2175 securityAuth django unauth view
medium System graph security auth conf 1.00 Django view `wishlist` may be unauthenticated — cars/views.py:2146
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`.
cars/views.py:2146 securityAuth django unauth view
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for bill in …` triggers a query per row — site_cars/migrations/0015_backfill_bill_items.py:10
The loop iterates a Django queryset and accesses `bill.items.exists` 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…
site_cars/migrations/0015_backfill_bill_items.py:10 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for dom in …` triggers a query per row — tenants/management/commands/gsc_register.py:81
The loop iterates a Django queryset and accesses `dom.domain.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries ins…
tenants/management/commands/gsc_register.py:81 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for item in …` triggers a query per row — cars/views.py:2158
The loop iterates a Django queryset and accesses `item.car.pk` 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 instead …
cars/views.py:2158 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — cars/views.py:1177
The loop iterates a Django queryset and accesses `m.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
cars/views.py:1177 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — cars/views.py:1198
The loop iterates a Django queryset and accesses `m.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
cars/views.py:1198 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — cars/views.py:1218
The loop iterates a Django queryset and accesses `m.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
cars/views.py:1218 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for m in …` triggers a query per row — cars/views.py:1238
The loop iterates a Django queryset and accesses `m.name.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries instead…
cars/views.py:1238 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for r in …` triggers a query per row — cars/management/commands/merge_brand_dupes.py:140
The loop iterates a Django queryset and accesses `r.name_ar.strip` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries inst…
cars/management/commands/merge_brand_dupes.py:140 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for t in …` triggers a query per row — site_cars/views.py:2031
The loop iterates a Django queryset and accesses `t.domains.first` 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…
site_cars/views.py:2031 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 security security conf 1.00 Public display field 'first_name' saved without validation in cars/views.py:2043
`first_name` is assigned directly from request field `first_name`. Public labels that accept URLs, HTML-like text, control characters, or bidi overrides can become trusted-looking phishing links in emails/UI even when templates escape HTML.
cars/views.py:2043 Input validationDisplay name validationSecurity public display name unvalidated
medium System graph security security conf 1.00 Public display field 'last_name' saved without validation in cars/views.py:2044
`last_name` is assigned directly from request field `last_name`. Public labels that accept URLs, HTML-like text, control characters, or bidi overrides can become trusted-looking phishing links in emails/UI even when templates escape HTML.
cars/views.py:2044 Input validationDisplay name validationSecurity public display name unvalidated
medium System graph security security conf 1.00 Public display field 'name' saved without validation in site_shop/views.py:131
`name` is assigned directly from request field `name`. Public labels that accept URLs, HTML-like text, control characters, or bidi overrides can become trusted-looking phishing links in emails/UI even when templates escape HTML.
site_shop/views.py:131 Input validationDisplay name validationSecurity public display name unvalidated
medium System graph security security conf 1.00 Public display field 'name' saved without validation in tenants/views.py:20
`name` is assigned directly from request field `name`. Public labels that accept URLs, HTML-like text, control characters, or bidi overrides can become trusted-looking phishing links in emails/UI even when templates escape HTML.
tenants/views.py:20 Input validationDisplay name validationSecurity public display name unvalidated
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
3 test file(s) for 226 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 9 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 14 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: site_shop/models.py:save, site_shop/models.py:save This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
14 occurrences
repo-level (14 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: site_cars/models.py:save, site_cars/models.py:save, site_cars/models.py:save This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
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: tenants/models.py:save, tenants/models.py:save, tenants/models.py:save, tenants/models.py:save 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…
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: cars/admin.py:get_queryset, cars/admin.py:get_queryset, cars/admin.py:get_queryset, cars/admin.py:get_queryset This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: cars/models.py:save, cars/models.py:save, cars/models.py:save, cars/models.py:save This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `car_list_v2` in cars/views.py:1076
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 `opt_copy` in cars/management/commands/import_auction_json.py:441
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 `opt_copy` in site_cars/views.py:1042
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: optimize_thumbnail
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
site_cars/image_utils.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: send_messages
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
site_cars/email_backend.py:14
low System graph quality Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo hardeningGenerated repo pattern
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 quality Integrity conf 1.00 Stub function `delete` (body is just `pass`/`return`) — tenants/models.py:288
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `noop` (body is just `pass`/`return`) — site_cars/migrations/0015_backfill_bill_items.py:25
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `noop` (body is just `pass`/`return`) — tenants/migrations/0030_globalexchangerates.py:18
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: ANY /accessories/
`site_shop/urls.py` declares `ANY /accessories/` 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 /accessories/<int:pk>/
`site_shop/urls.py` declares `ANY /accessories/<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 /auctions/browse/
`site_cars/urls.py` declares `ANY /auctions/browse/` 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/
`site_cars/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/damaged-cars/delete-unsold/
`site_cars/urls.py` declares `ANY /dashboard/damaged-cars/delete-unsold/` 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/delete-auctions/
`site_cars/urls.py` declares `ANY /dashboard/delete-auctions/` 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/import-happycar/
`site_cars/urls.py` declares `ANY /dashboard/import-happycar/` 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/shop/
`site_shop/urls.py` declares `ANY /dashboard/shop/` 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/shop/<int:pk>/delete-image/<int:image_id>/
`site_shop/urls.py` declares `ANY /dashboard/shop/<int:pk>/delete-image/<int:image_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /dashboard/shop/<int:pk>/delete/
`site_shop/urls.py` declares `ANY /dashboard/shop/<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 /dashboard/shop/<int:pk>/edit/
`site_shop/urls.py` declares `ANY /dashboard/shop/<int:pk>/edit/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /dashboard/shop/<int:pk>/toggle-stock/
`site_shop/urls.py` declares `ANY /dashboard/shop/<int:pk>/toggle-stock/` 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/shop/add/
`site_shop/urls.py` declares `ANY /dashboard/shop/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 /dashboard/shop/import/
`site_shop/urls.py` declares `ANY /dashboard/shop/import/` 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 /faq/
`site_cars/urls.py` declares `ANY /faq/` 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 /faq/manage/
`site_cars/urls.py` declares `ANY /faq/manage/` 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 /inbox/
`site_cars/urls.py` declares `ANY /inbox/` 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 /inbox/<int:pk>/
`site_cars/urls.py` declares `ANY /inbox/<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 /inbox/compose/
`site_cars/urls.py` declares `ANY /inbox/compose/` 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 /my-orders/
`site_cars/urls.py` declares `ANY /my-orders/` 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 /my-orders/<int:pk>/
`site_cars/urls.py` declares `ANY /my-orders/<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 /order/<int:pk>/
`site_cars/urls.py` declares `ANY /order/<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 /our-cars/
`site_cars/urls.py` declares `ANY /our-cars/` 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 /our-cars/<int:pk>/
`site_cars/urls.py` declares `ANY /our-cars/<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 /our-cars/<int:pk>/delete-image/<int:image_id>/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/delete-image/<int:image_id>/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /our-cars/<int:pk>/delete/
`site_cars/urls.py` declares `ANY /our-cars/<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 /our-cars/<int:pk>/edit/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/edit/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /our-cars/<int:pk>/invoice/<int:bill_pk>/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/invoice/<int:bill_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 /our-cars/<int:pk>/invoice/<int:bill_pk>/edit/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/invoice/<int:bill_pk>/edit/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /our-cars/<int:pk>/invoice/<int:bill_pk>/shipment/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/invoice/<int:bill_pk>/shipment/` 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 /our-cars/<int:pk>/invoice/new/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/invoice/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 /our-cars/<int:pk>/status/
`site_cars/urls.py` declares `ANY /our-cars/<int:pk>/status/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /our-cars/add/
`site_cars/urls.py` declares `ANY /our-cars/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 /our-cars/save/<int:api_car_id>/
`site_cars/urls.py` declares `ANY /our-cars/save/<int:api_car_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 /parts/
`site_shop/urls.py` declares `ANY /parts/` 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 /parts/<int:pk>/
`site_shop/urls.py` declares `ANY /parts/<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 /rate-site/
`site_cars/urls.py` declares `ANY /rate-site/` 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 /rate/<int:pk>/
`site_cars/urls.py` declares `ANY /rate/<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 /rating/<int:pk>/approve/
`site_cars/urls.py` declares `ANY /rating/<int:pk>/approve/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /rating/<int:pk>/reject/
`site_cars/urls.py` declares `ANY /rating/<int:pk>/reject/` 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 /send-email/
`site_cars/urls.py` declares `ANY /send-email/` 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 /sold-cars/
`site_cars/urls.py` declares `ANY /sold-cars/` 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/orders/
`site_cars/urls.py` declares `ANY /staff/orders/` 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/orders/<int:pk>/update/
`site_cars/urls.py` declares `ANY /staff/orders/<int:pk>/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 /staff/questions/
`site_cars/urls.py` declares `ANY /staff/questions/` 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/questions/<int:pk>/answer/
`site_cars/urls.py` declares `ANY /staff/questions/<int:pk>/answer/` 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/ratings/
`site_cars/urls.py` declares `ANY /staff/ratings/` 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 /track/<str:receipt_number>/
`site_cars/urls.py` declares `ANY /track/<str:receipt_number>/` 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 /upload-auction/
`site_cars/urls.py` declares `ANY /upload-auction/` 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 /upload-auction/delete-expired/
`site_cars/urls.py` declares `ANY /upload-auction/delete-expired/` 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: cars/utils.py (1711 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: cars/views.py (3392 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: site_cars/happycar/transelations.py (3583 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: site_cars/views.py (2046 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/42291b3c-1e24-4074-b7fc-dd530abb1a93/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/42291b3c-1e24-4074-b7fc-dd530abb1a93/

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.