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

Scan timing: clone 8.2s · analysis 25.96s · 47.5 MB · GitHub API rate-limit (preflight)

git/git

https://github.com/git/git · scanned 2026-06-05 09:29 UTC (5 days, 18 hours ago) · 10 languages

437 raw signals (127 security + 310 graph) 11/13 scanners ran 38th percentile · C · large (100-500K LoC)

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

Complete repo analysis

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

JSON
Combined
73.1
/100
Security checks
83
39 findings
System graph
63
88.9% cov · 126 findings
Critical
6
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 15.0 0.20 3.00
documentation_score 45.0 0.15 6.75
practices_score 77.0 0.15 11.55
code_quality 54.0 0.10 5.40
Overall 1.00 64.5
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 6 High 8 Medium 87 Low 44 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 39 System graph 126 Crowd 0 Layer: Quality 61 Security 31 Software 10 Cicd 2 Api 1 Network 60

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in t/t5580-unc-paths.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in t/t5580-unc-paths.sh:11; move to env var / secrets manager.
t/t5580-unc-paths.sh:11
#2
Possible secret in t/lib-gitweb.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in t/lib-gitweb.sh:8; move to env var / secrets manager.
t/lib-gitweb.sh:8
#3
Insecure pattern 'tls_verify_false' in git-p4.py:1840
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
git-p4.py:1840
#4
Privileged port 256 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t3311-notes-merge-fanout.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t3311-notes-merge-fanout.sh
#5
Privileged port 26 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t3311-notes-merge-fanout.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t3311-notes-merge-fanout.sh
#6
Privileged port 13 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t8008-blame-formats.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t8008-blame-formats.sh
#7
Privileged port 3 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t7501-commit-basic-functionality.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t7501-commit-basic-functionality.sh
#8
Privileged port 23 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t1400-update-ref.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t1400-update-ref.sh
#9
Privileged port 30 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t1400-update-ref.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t1400-update-ref.sh
#10
Privileged port 31 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in t/t1400-update-ref.sh is a real port, change the binding to ≥1024 or run behind a proxy.
t/t1400-update-ref.sh

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/1c561cf2-5600-4ddc-8e44-4c536211ab9a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1c561cf2-5600-4ddc-8e44-4c536211ab9a/

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.