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

vedant-moxie/DevGenie

https://github.com/vedant-moxie/DevGenie · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

49 raw signals (0 security + 49 graph)

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

Complete repo analysis

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

JSON
Combined
49.0
/100
Security checks
49
0 findings
System graph
49
100.0% cov · 48 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 9 Medium 12 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 48 Crowd 0 Layer: Software 11 Frontend 3 Hardware 5 Security 6 Cicd 1 Quality 13 Api 9
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 49.0/100 with 100.0% coverage. It contains 344 nodes across 17 cross-layer flows, written primarily in mixed languages. Engine surfaced 49 findings — concentrated in quality (13), software (11), api (9). Risk profile is high: 0 critical, 9 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 45 of 48 actionable findings. 49 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 System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects (frontend/src/app/chat/page.tsx:141)
`frontend/src/app/chat/page.tsx:141` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects (frontend/src/app/dashboard/page.tsx:125)
`frontend/src/app/dashboard/page.tsx:125` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects (frontend/src/app/graph/page.tsx:128)
`frontend/src/app/graph/page.tsx:128` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects (frontend/src/app/settings/page.tsx:65)
`frontend/src/app/settings/page.tsx:65` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/projects (frontend/src/app/settings/page.tsx:79)
`frontend/src/app/settings/page.tsx:79` calls `GET /api/projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://gitlab.com/oauth/token (frontend/src/app/api/auth/[...nextauth]/route.ts:10)
`frontend/src/app/api/auth/[...nextauth]/route.ts:10` calls `POST https://gitlab.com/oauth/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/gitlab.com/oauth/token` If this points at an external API, pref…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — ui/main.py:96
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
ui/main.py:96 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest` without auth dependency — ui/main.py:136
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
ui/main.py:136 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `risk` without auth dependency — ui/main.py:222
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
ui/main.py:222 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/Markdown.tsx:24
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/api/chat/route.ts:28
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/chat/page.tsx:231
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
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, tests. 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 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/Markdown.tsx:24
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/Markdown.tsx:24 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ui/index.html:278
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
ui/index.html:278 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in ui/index.html:285
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
ui/index.html:285 Insert adjacent html
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 50 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 19 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_MODEL`, `BACKEND_URL`, `DISABLE_GITLAB_MCP`, `ENABLE_CLOUD_TRACE`, `FETCH_DIFFS`, `GITLAB_CLIENT_ID`, `GITLAB_CLIENT_SECRET`, `GITLAB_MCP_STDIO` + 11 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 56 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 hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 4, 11
frontend/Dockerfile:4, 11 (2 hits)
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:3 containersPinned dependencies
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/chat/page.tsx:957
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/app/dashboard/page.tsx:828
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `aiplatform_v1` in ingestion/vector_index.py:21
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: commit_diff
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/live.py:109
low System graph software Dead code conf 1.00 Possibly dead Python function: explain_blame
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:234
low System graph software Dead code conf 1.00 Possibly dead Python function: explain_code_decision
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:142
low System graph software Dead code conf 1.00 Possibly dead Python function: ingest_commits
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ingestion/main.py:214
low System graph software Dead code conf 1.00 Possibly dead Python function: ingest_issues
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ingestion/main.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: list_reverted_changes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:267
low System graph software Dead code conf 1.00 Possibly dead Python function: lookup_reference
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: onboarding_brief
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:172
low System graph software Dead code conf 1.00 Possibly dead Python function: repo_structure
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/live.py:157
low System graph software Dead code conf 1.00 Possibly dead Python function: search_decision_history
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent/tools.py:73
low System graph software Dead code conf 1.00 Possibly dead Python function: warmup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
ingestion/vector_index.py:49
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: GET /
`ui/main.py` declares `GET /` 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: GET /ingest/status
`ui/main.py` declares `GET /ingest/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: POST /webhook
`webhook/main.py` declares `POST /webhook` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
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/abbf032f-ed4f-4fc3-954e-8ac77716577a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/abbf032f-ed4f-4fc3-954e-8ac77716577a/

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.