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

sujitojha1/repo-genesis

https://github.com/sujitojha1/repo-genesis · scanned 2026-06-16 00:25 UTC (2 months, 2 weeks ago)

51 raw signals (0 security + 51 graph)

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

Complete repo analysis

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

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

Showing 35 of 47 actionable findings. 51 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 security auth conf 1.00 FastAPI POST `chat_batch` without auth dependency — gateway/main.py:618
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
gateway/main.py:618 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — gateway/main.py:349
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
gateway/main.py:349 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `embed` without auth dependency — gateway/main.py:698
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
gateway/main.py:698 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `vision` without auth dependency — gateway/main.py:641
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
gateway/main.py:641 securityAuth fastapi unauth mutation
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 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 security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in .claude/skills/codebase-to-course/references/main.js:193
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
.claude/skills/codebase-to-course/references/main.js:193 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in course/main.js:193
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
course/main.js:193 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in gateway/static/dashboard.html:150
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
gateway/static/dashboard.html:150 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — code/gateway.py:46
`subprocess.Popen(...)` 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 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 26 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `CEREBRAS_API_KEY`, `CEREBRAS_MODEL`, `EMBED_FALLBACK_MODEL`, `EMBED_FALLBACK_PROVIDER`, `EMBED_OLLAMA_MODEL`, `EMBED_ORDER`, `GATEWAY_V9_PORT`, `GEMINI_API_KEY` + 18 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 76 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 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: code/browser/dom.py:legend_line, code/browser/dom.py:legend 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.
5 occurrences
repo-level (5 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: gateway/embedders.py:embed, gateway/embedders.py:embed, gateway/embedders.py:embed 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: gateway/providers.py:chat, gateway/providers.py:chat, gateway/providers.py:chat, gateway/providers.py:chat 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 …
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: chat_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gateway/client.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: cost_by_agent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
code/browser/client.py:133
low System graph software Dead code conf 1.00 Possibly dead Python function: cost_by_agent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gateway/client.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: read_node
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
code/persistence.py:161
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 /
`gateway/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 /help
`gateway/main.py` declares `GET /help` 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 /v1/calls
`gateway/main.py` declares `GET /v1/calls` 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 /v1/capabilities
`gateway/main.py` declares `GET /v1/capabilities` 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 /v1/cost/by_agent
`gateway/main.py` declares `GET /v1/cost/by_agent` 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 /v1/embedders
`gateway/main.py` declares `GET /v1/embedders` 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 /v1/providers
`gateway/main.py` declares `GET /v1/providers` 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 /v1/routers
`gateway/main.py` declares `GET /v1/routers` 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 /v1/status
`gateway/main.py` declares `GET /v1/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 /v1/chat
`gateway/main.py` declares `POST /v1/chat` 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 /v1/chat/batch
`gateway/main.py` declares `POST /v1/chat/batch` 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 /v1/embed
`gateway/main.py` declares `POST /v1/embed` 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 /v1/vision
`gateway/main.py` declares `POST /v1/vision` 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/288edcf4-b66b-41b0-a0e5-b16338a5d9eb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/288edcf4-b66b-41b0-a0e5-b16338a5d9eb/

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.