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

BIZKON/risuy-ecosystem

https://github.com/BIZKON/risuy-ecosystem · scanned 2026-06-17 01:19 UTC (1 month, 2 weeks ago)

45 raw signals (0 security + 45 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +10.1 (diff) · 38 actionable findings from 1 signal source. 7 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 27 of 38 actionable findings. 45 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 `service_subscribe` without auth dependency — admin-panel/app.py:2671
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
admin-panel/app.py:2671 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `yookassa_webhook` without auth dependency — admin-panel/app.py:2731
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
admin-panel/app.py:2731 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — admin-panel/static/thread.js: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 Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
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: admin-panel/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: bot-telegram/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: 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 'direct_innerhtml_assignment' in admin-panel/static/thread.js:37
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
admin-panel/static/thread.js:37 Direct innerhtml assignment
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 quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 32 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 34 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_ID`, `AI_GATEWAY_TOKEN`, `DEFAULT_TENANT_SLUG`, `EMBEDDER_TOKEN`, `EMBEDDER_URL`, `FFMPEG_BIN`, `LOGIN_ALLOWLIST_CIDR`, `MAX_PRODUCT_FILE_MB` + 26 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 26 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 3 occurrences 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.
3 files, 3 locations
Dockerfile:12
admin-panel/Dockerfile:7
bot-telegram/Dockerfile:1
containersPinned dependencies
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/metering_smoke.py:check, scripts/metering_worker_smoke.py:check 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.
6 occurrences
repo-level (6 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: admin-panel/app.py:logout, admin-panel/app.py:export_masked, admin-panel/app.py:subscription_cancel 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…
duplicatesduplication
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 `len_old` in admin-panel/db.py:369
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 `t_legacy` in scripts/metering_smoke.py:87
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: list_knowledge_bases
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
admin-panel/timeweb_ai.py:120
low System graph software Dead code conf 1.00 Possibly dead Python function: list_models
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
admin-panel/timeweb_ai.py:114
low System graph software Dead code conf 1.00 Possibly dead Python function: require_session
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
admin-panel/app.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: resolve_lead_id
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot-telegram/db.py:206
low System graph software Dead code conf 1.00 Possibly dead Python function: unsubscribe_markup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot-telegram/messaging.py:37
low System graph quality Complexity conf 1.00 Very large file: admin-panel/app.py (3953 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: admin-panel/db.py (3019 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: bot-telegram/db.py (1301 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/ba81859e-b765-453e-8678-4003dbabc242/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ba81859e-b765-453e-8678-4003dbabc242/

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.