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

Scan timing: clone 1.33s · analysis 4.34s · 1.2 MB · GitHub API rate-limit (preflight)

mautrix/meta

https://github.com/mautrix/meta · scanned 2026-06-05 17:40 UTC (4 days, 22 hours ago) · 10 languages

75 raw signals (51 security + 24 graph) 12th percentile · Go · medium (20-100K LoC) System graph score 69 (lower by 11)

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

Complete repo analysis

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

JSON
Combined
68.9
/100
Security checks
69
44 findings
System graph
69
100.0% cov · 10 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 100.0 0.15 15.00
security_score 48.1 0.25 12.03
testing_score 0.0 0.20 0.00
documentation_score 70.0 0.15 10.50
practices_score 89.0 0.15 13.35
code_quality 70.0 0.10 7.00
Overall 1.00 57.9
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 29 Medium 5 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 44 System graph 10 Crowd 0 Layer: Cicd 6 Security 3 Quality 11 Software 27 Api 1 Data 1 Hardware 4 Frontend 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 1 finding
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.
1 matching finding on this repo
  • high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… pkg/msgconv/media_notls.go:14
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/71e2ff02-42ce-44a5-bdbc-87593cc371ba/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/71e2ff02-42ce-44a5-bdbc-87593cc371ba/

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.