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

sostrowsk/dj-data-room

https://github.com/sostrowsk/dj-data-room · scanned 2026-06-16 00:18 UTC (2 months, 2 weeks ago)

87 raw signals (0 security + 87 graph)

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

Complete repo analysis

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

JSON
Combined
75.7
/100
Security checks
76
0 findings
System graph
76
88.9% cov · 70 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 8 Low 55 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 70 Crowd 0 Layer: Software 13 Frontend 1 Security 1 Cicd 1 Quality 16 Api 38
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 75.7/100 with 88.9% coverage. It contains 1016 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 87 findings — concentrated in api (38), quality (33), software (13). Risk profile is low: 0 critical, 0 high, 8 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

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

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci. 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 Integrity conf 1.00 Likely N+1 query: `for document in …` triggers a query per row — data_room/tasks/index_document.py:918
The loop iterates a Django queryset and accesses `document.file.name` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries i…
data_room/tasks/index_document.py:918 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for form in …` triggers a query per row — data_room/views/hx/confirm_clients.py:71
The loop iterates a Django queryset and accesses `form.cleaned_data.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 querie…
data_room/views/hx/confirm_clients.py:71 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for old_zip in …` triggers a query per row — data_room/tasks/project_zip.py:64
The loop iterates a Django queryset and accesses `old_zip.zip_file.delete` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 quer…
data_room/tasks/project_zip.py:64 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for old_zip in …` triggers a query per row — data_room/views/api/project_zip.py:81
The loop iterates a Django queryset and accesses `old_zip.zip_file.delete` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 quer…
data_room/views/api/project_zip.py:81 N plus onePerformance
medium System graph quality Integrity conf 1.00 Likely N+1 query: `for project in …` triggers a query per row — data_room/tasks/index_document.py:1022
The loop iterates a Django queryset and accesses `project.protected_documents.all` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in …
data_room/tasks/index_document.py:1022 N plus onePerformance
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: data_room/admin.py:rerun_full_pipeline, data_room/admin.py:rerun_full_pipeline 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.
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: data_room/decorators.py:decorator, data_room/decorators.py:decorator, data_room/decorators.py:decorator 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…
2 occurrences
repo-level (2 hits)
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: data_room/views/protected_document.py:protected_document_reviewed, data_room/views/protected_document.py:protected_document_disabled, data_room/views/protected_document.py:protected_document_enable, data_room/views/protected_document.py:toggle_ai Thi…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: client_document_delete
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:303
low System graph software Dead code conf 1.00 Possibly dead Python function: client_document_disabled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:275
low System graph software Dead code conf 1.00 Possibly dead Python function: client_document_enable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:291
low System graph software Dead code conf 1.00 Possibly dead Python function: client_document_reviewed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:263
low System graph software Dead code conf 1.00 Possibly dead Python function: company_names_match
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/services/company_names.py:112
low System graph software Dead code conf 1.00 Possibly dead Python function: compress_pdf_bytes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/utils.py:104
low System graph software Dead code conf 1.00 Possibly dead Python function: document_chunks_view
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/document_chunks.py:12
low System graph software Dead code conf 1.00 Possibly dead Python function: protected_document_delete
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:176
low System graph software Dead code conf 1.00 Possibly dead Python function: protected_document_disabled
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:132
low System graph software Dead code conf 1.00 Possibly dead Python function: protected_document_enable
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:148
low System graph software Dead code conf 1.00 Possibly dead Python function: protected_document_reviewed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:117
low System graph software Dead code conf 1.00 Possibly dead Python function: render_orgchart_png
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/helpers/orgchart.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: toggle_ai
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
data_room/views/protected_document.py:162
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: ANY /chunks/<int:pk>/
`data_room/urls.py` declares `ANY /chunks/<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 /client-doc/delete/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/delete/<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 /client-doc/disabled/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/disabled/<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 /client-doc/enable/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/enable/<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 /client-doc/original/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/original/<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 /client-doc/page/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/page/<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 /client-doc/pdf/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/pdf/<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 /client-doc/reviewed/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/reviewed/<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 /client-doc/toggle-ai/<int:pk>/
`data_room/urls.py` declares `ANY /client-doc/toggle-ai/<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 /count-indexed-chunks/
`data_room/urls.py` declares `ANY /count-indexed-chunks/` 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 /create/<int:pk>/
`data_room/urls.py` declares `ANY /create/<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 /delete-all/<int:pk>/
`data_room/urls.py` declares `ANY /delete-all/<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 /delete/<int:pk>/
`data_room/urls.py` declares `ANY /delete/<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 /disabled/<int:pk>/
`data_room/urls.py` declares `ANY /disabled/<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 /document/<int:pk>/
`data_room/urls.py` declares `ANY /document/<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 /enable/<int:pk>/
`data_room/urls.py` declares `ANY /enable/<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 /hx/<int:pk>/edit-client/<int:document_pk>/
`data_room/urls.py` declares `ANY /hx/<int:pk>/edit-client/<int:document_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 /hx/<int:pk>/upload/client/
`data_room/urls.py` declares `ANY /hx/<int:pk>/upload/client/` 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 /hx/<int:pk>/upload/project/
`data_room/urls.py` declares `ANY /hx/<int:pk>/upload/project/` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /hx/close-modal/
`data_room/urls.py` declares `ANY /hx/close-modal/` 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 /hx/confirm-clients-client-doc/<int:document_pk>/
`data_room/urls.py` declares `ANY /hx/confirm-clients-client-doc/<int:document_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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /hx/edit-client-client-doc/<int:document_pk>/
`data_room/urls.py` declares `ANY /hx/edit-client-client-doc/<int:document_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /hx/empty/<int:pk>/
`data_room/urls.py` declares `ANY /hx/empty/<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 /hx/project-zip-button/<int:pk>/
`data_room/urls.py` declares `ANY /hx/project-zip-button/<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 /hx/skip-clients-client-doc/<int:document_pk>/
`data_room/urls.py` declares `ANY /hx/skip-clients-client-doc/<int:document_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /hx/toggle-company-link/<int:project_pk>/<int:client_pk>/
`data_room/urls.py` declares `ANY /hx/toggle-company-link/<int:project_pk>/<int:client_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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /hx/trigger-extraction-client-doc/<int:document_pk>/
`data_room/urls.py` declares `ANY /hx/trigger-extraction-client-doc/<int:document_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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /index-documents/
`data_room/urls.py` declares `ANY /index-documents/` 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 /original/<int:pk>/
`data_room/urls.py` declares `ANY /original/<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 /page/<int:pk>/
`data_room/urls.py` declares `ANY /page/<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 /pdf/<int:pk>/
`data_room/urls.py` declares `ANY /pdf/<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 /project-zip/download/<int:pk>/
`data_room/urls.py` declares `ANY /project-zip/download/<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 /project-zip/progress/<int:pk>/
`data_room/urls.py` declares `ANY /project-zip/progress/<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 /project-zip/start/<int:pk>/
`data_room/urls.py` declares `ANY /project-zip/start/<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 /redirect/<int:pk>/
`data_room/urls.py` declares `ANY /redirect/<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 /reset-index/
`data_room/urls.py` declares `ANY /reset-index/` 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 /reviewed/<int:pk>/
`data_room/urls.py` declares `ANY /reviewed/<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 /toggle-ai/<int:pk>/
`data_room/urls.py` declares `ANY /toggle-ai/<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
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/f33bf782-06ec-4e35-b990-0dee6857855f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f33bf782-06ec-4e35-b990-0dee6857855f/

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.