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

SLYAllan/uwutcg-bot

https://github.com/SLYAllan/uwutcg-bot · scanned 2026-06-16 00:15 UTC (2 months, 2 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, 2 weeks ago · v1 · 24 actionable findings from 1 signal source. 19 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

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

Showing 22 of 24 actionable findings. 43 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.

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 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 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 7 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: mcr.microsoft.com/playwright/python:v1.47.0-jammy
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:2 containersPinned dependencies
low System graph quality Tests conf 1.00 Low test-to-source ratio
9 tests / 42 src (ratio 0.21).
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: bot/config.py:get_settings, bot/config.py:get 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 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: as_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot/config.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot/ui/alerts.py:56
low System graph software Dead code conf 1.00 4 occurrences Possibly dead Python function: cog_unload
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
4 files, 4 locations
bot/cogs/arbitrage.py:27
bot/cogs/monitor.py:37
bot/cogs/sealed.py:25
bot/cogs/tracking.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot/services/grading_roi.py:65
low System graph software Dead code conf 1.00 Possibly dead Python function: set_listing_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot/db/database.py:109
low System graph software Dead code conf 1.00 13 occurrences Possibly dead Python function: setup
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
bot/cogs/arbitrage.py:120
bot/cogs/calc.py:205
bot/cogs/cards.py:53
bot/cogs/config.py:81
bot/cogs/daily.py:165
bot/cogs/grading.py:64
bot/cogs/info.py:136
bot/cogs/knowledge.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: setup_hook
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bot/main.py:83
low System graph software Dead code conf 1.00 Possibly dead Python function: t_cardmarket
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_scrapers.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: t_ebay
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_scrapers.py:36
low System graph software Dead code conf 1.00 Possibly dead Python function: t_ebay_sold
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_scrapers.py:44
low System graph software Dead code conf 1.00 Possibly dead Python function: t_japan
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_scrapers.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: t_vinted
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/smoke_scrapers.py:50
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
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/d5fa0ad0-ff1b-4322-bb41-2ee57c01e064/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d5fa0ad0-ff1b-4322-bb41-2ee57c01e064/

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.