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

samprak-ai/genai-intel

https://github.com/samprak-ai/genai-intel · scanned 2026-06-16 00:01 UTC (2 months, 3 weeks ago)

52 raw signals (0 security + 52 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 52 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 43 of 52 actionable findings. 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: POST /api/auth/login (dashboard/app/login/page.tsx:22)
`dashboard/app/login/page.tsx:22` calls `POST /api/auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
Dockerfile:16 containersRemote installer
high System graph security auth conf 1.00 FastAPI POST `ask` without auth dependency — api/routers/ask.py:131
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
api/routers/ask.py:131 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/attribution/attribution_engine.py:918
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/attribution/attribution_engine.py:918 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/discovery/funding_discovery.py:506
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/discovery/funding_discovery.py:506 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in app/resolution/domain_resolver.py:185
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
app/resolution/domain_resolver.py:185 Tls verify false
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in scripts/re_resolve_domains.py:87
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
scripts/re_resolve_domains.py:87 Tls verify false
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — dashboard/lib/api.ts:37
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 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 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
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 26 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. 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 256 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 Docker base image is tag-pinned but not digest-pinned: python:3.12-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:8 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
7 tests / 64 src (ratio 0.11).
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 software Dead code conf 1.00 Possibly dead Python function: create_trigger
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/database.py:494
low System graph software Dead code conf 1.00 Possibly dead Python function: log
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/core/database.py:393
low System graph software Dead code conf 1.00 Possibly dead Python function: rank_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/resolution/domain_resolver.py:434
low System graph software Dead code conf 1.00 Possibly dead Python function: score
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
app/discovery/funding_discovery.py:301
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
api/deps.py:32
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 /
`api/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 /ai-distribution
`api/routers/analytics.py` declares `GET /ai-distribution` 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 /cloud-distribution
`api/routers/analytics.py` declares `GET /cloud-distribution` 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 /provider-changes
`api/routers/analytics.py` declares `GET /provider-changes` 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 /recent-funding
`api/routers/analytics.py` declares `GET /recent-funding` 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 /runs
`api/routers/pipeline.py` declares `GET /runs` 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 /runs/{run_id}
`api/routers/pipeline.py` declares `GET /runs/{run_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: GET /search-usage
`api/routers/analytics.py` declares `GET /search-usage` 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 /signal-effectiveness
`api/routers/analytics.py` declares `GET /signal-effectiveness` 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 /summary
`api/routers/analytics.py` declares `GET /summary` 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 /{startup_id}
`api/routers/startups.py` declares `GET /{startup_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: PATCH /{startup_id}
`api/routers/startups.py` declares `PATCH /{startup_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: POST /
`api/routers/startups.py` declares `POST /` 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 /api/auth/verify
`api/main.py` declares `POST /api/auth/verify` 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 /ask
`api/routers/ask.py` declares `POST /ask` 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 /trigger
`api/routers/pipeline.py` declares `POST /trigger` 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 /{startup_id}/re-attribute
`api/routers/startups.py` declares `POST /{startup_id}/re-attribute` 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: app/attribution/attribution_engine.py (4055 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/7acdecf7-7f34-4318-9c69-357a7c784716/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7acdecf7-7f34-4318-9c69-357a7c784716/

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.