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
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 45.17s for a 75.6 MB repo slow.
  • Repobility's analysis ran in 9.02s after the clone landed.

rikkahub/rikkahub

https://github.com/rikkahub/rikkahub · scanned 2026-05-31 01:26 UTC (2 weeks, 1 day ago) · 10 languages

222 raw signals (120 security + 102 graph) 11/13 scanners ran 57th percentile · Kotlin · large (100-500K LoC) System graph score 79 (lower by 7)

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

Complete repo analysis

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

JSON
Combined
82.6
/100
Security checks
86
41 findings
System graph
79
77.8% cov · 48 findings
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 23.0 0.20 4.60
documentation_score 71.0 0.15 10.65
practices_score 75.0 0.15 11.25
code_quality 79.0 0.10 7.90
Overall 1.00 72.2
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 15 Medium 3 Low 36 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 41 System graph 48 Crowd 0 Layer: Quality 31 Security 6 Software 37 Cicd 1 Api 1 Frontend 13

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: web-ui/vite.config.ts
  • low File has no detected symbols: web-ui/react-router.config.ts
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/fff71f28-48b8-4e50-b035-1c9f771bcef0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/fff71f28-48b8-4e50-b035-1c9f771bcef0/

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.