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

Scan timing: clone 4.06s · analysis 1.12s · 16.8 MB · GitHub API rate-limit (preflight)

shiyu-coder/Kronos

https://github.com/shiyu-coder/Kronos.git · scanned 2026-05-24 01:24 UTC (2 weeks, 6 days ago) · 10 languages

178 raw signals (72 security + 106 graph) 43rd percentile · Python · small (2-20K LoC) System graph score 82 (lower by 17)

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

Complete repo analysis

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

JSON
Combined
77.3
/100
Security checks
73
20 findings
System graph
82
88.9% cov · 36 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 55.0 0.15 8.25
security_score 98.0 0.25 24.50
testing_score 47.0 0.20 9.40
documentation_score 78.0 0.15 11.70
practices_score 42.0 0.15 6.30
code_quality 45.4 0.10 4.54
Overall 1.00 64.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 9 Medium 6 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 20 System graph 36 Crowd 0 Layer: Quality 24 Security 12 Software 11 Frontend 1 Cicd 1 Api 7

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.

Duplicates & near-duplicates 3 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
3 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 4 places
View all duplicates & near-duplicates findings →
Config drift 4 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.
4 matching findings on this repo
  • medium No CI/CD configuration found
  • low Possibly dead Python function: update_config finetune_csv/config_loader.py:81
  • low Possibly dead Python function: save_config finetune_csv/config_loader.py:93
  • low Possibly dead Python function: print_config finetune_csv/config_loader.py:101
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/5c477c06-2fcd-427a-8d6c-b93ac760fef7/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5c477c06-2fcd-427a-8d6c-b93ac760fef7/

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.