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
19 of your 64 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.92s · analysis 14.12s · 0.6 MB · GitHub preflight 433ms

YUxiangLuo/miao

https://github.com/YUxiangLuo/miao · scanned 2026-06-05 14:13 UTC (5 days, 5 hours ago) · 10 languages

111 raw signals (55 security + 56 graph) 17th percentile · Rust · small (2-20K LoC) System graph score 70 (lower by 15)

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

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 52 actionable findings from 2 signal sources. 30 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
67.6
/100
Security checks
66
39 findings
System graph
70
77.8% cov · 13 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 42.7 0.25 10.68
testing_score 20.0 0.20 4.00
documentation_score 42.0 0.15 6.30
practices_score 69.0 0.15 10.35
code_quality 79.4 0.10 7.94
Overall 1.00 54.3
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 3 High 23 Medium 9 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 39 System graph 13 Crowd 0 Layer: Quality 9 Security 14 Software 25 Cicd 3 Api 1

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Config drift 2 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
2 matching findings on this repo
  • low File has no detected symbols: frontend/vite.config.js
  • low File has no detected symbols: frontend/eslint.config.js
View all config drift findings →
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/ea6a3555-7212-422d-929f-bd9c50e55512/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/ea6a3555-7212-422d-929f-bd9c50e55512/

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.