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

RedRightH/Steel_Trade_Intelligence_System

https://github.com/RedRightH/Steel_Trade_Intelligence_System · scanned 2026-06-15 23:49 UTC (2 months, 3 weeks ago)

43 raw signals (0 security + 43 graph)

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

Complete repo analysis

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

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

Showing 37 of 43 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 security auth conf 1.00 FastAPI POST `cache_clear` without auth dependency — api.py:180
`@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.py:180 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gravity_scenario` without auth dependency — api.py:203
`@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.py:203 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `query_impact` without auth dependency — api.py:154
`@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.py:154 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `query` without auth dependency — api.py:110
`@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.py:110 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'exec_used' in steel_rag/data_agent.py:560
Found a known-risky pattern (exec_used). Review and replace if possible.
steel_rag/data_agent.py:560 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in steel_rag/tariff_agent.py:648
Found a known-risky pattern (exec_used). Review and replace if possible.
steel_rag/tariff_agent.py:648 Exec used
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 'cors_wildcard' in api.py:46
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
api.py:46 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/index.html:166
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/index.html:166 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — vllm/setup_vllm_colab.py:48
`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 5 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `PINECONE_API_KEY`, `PINECONE_CLOUD`, `PINECONE_INDEX_NAME`, `PINECONE_REGION`, `VLLM_BASE_URL`. 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: 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 quality Debug conf 1.00 Debug logging residue appears in source files
Found 672 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 Tests conf 1.00 Low test-to-source ratio
5 tests / 32 src (ratio 0.16).
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 `baseline_v1` in steel_rag/dashboard.py:7
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 `baseline_v1` in steel_rag/eval_harness.py:32
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 `baseline_v1` in steel_rag/run_eval.py:17
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 `ground_truth_v2` in steel_rag/eval/run_eval.py:42
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: is_answer_grounded
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/guardrails.py:102
low System graph software Dead code conf 1.00 Possibly dead Python function: is_followup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/memory.py:107
low System graph software Dead code conf 1.00 Possibly dead Python function: plot_country_comparison
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/data_agent.py:794
low System graph software Dead code conf 1.00 Possibly dead Python function: predict_top_scenarios
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/gravity_model.py:622
low System graph software Dead code conf 1.00 Possibly dead Python function: query_import_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/data_agent.py:1277
low System graph software Dead code conf 1.00 Possibly dead Python function: to_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/memory.py:125
low System graph software Dead code conf 1.00 Possibly dead Python function: warm_cache
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
steel_rag/semantic_cache.py:204
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 /cache/stats
`api.py` declares `GET /cache/stats` 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 /gravity/insights
`api.py` declares `GET /gravity/insights` 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 /cache/clear
`api.py` declares `POST /cache/clear` 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 /gravity/scenario
`api.py` declares `POST /gravity/scenario` 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 /query
`api.py` declares `POST /query` 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 /query/impact
`api.py` declares `POST /query/impact` 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: steel_rag/dashboard.py (1473 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: steel_rag/data_agent.py (1491 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/80d92a61-dcb7-42ef-b397-0b10bc25305c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/80d92a61-dcb7-42ef-b397-0b10bc25305c/

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.