ghostty-org/ghostty

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.

87 of your 121 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 28.47s · analysis 27.1s · 80.8 MB · GitHub API rate-limit (preflight)

https://github.com/ghostty-org/ghostty · scanned 2026-06-05 10:18 UTC (5 days, 15 hours ago) · 10 languages

134 raw signals (106 security + 28 graph) 11/13 scanners ran 60th percentile · Swift · medium (20-100K LoC) System graph score 88 (lower by 15)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 14 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	100.0	0.25	25.00
`testing_score`	34.0	0.20	6.80
`documentation_score`	82.0	0.15	12.30
`practices_score`	84.0	0.15	12.60
`code_quality`	66.0	0.10	6.60
Overall		1.00	73.0

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 10 Medium 8 Low 9 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 35 System graph 14 Crowd 0 Layer: Cicd 8 Software 8 Quality 24 Security 4 Api 1 Network 3 Frontend 1

Exclude dismissed / FP Exclude test files

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.

Commented-out code 1 finding

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

1 matching finding on this repo

info Commented-code block (16 lines) in src/font/nerd_font_codegen.py:342

View all commented-out code 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/15245132-025c-481e-bc73-2d2f4b6d88a3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/15245132-025c-481e-bc73-2d2f4b6d88a3/

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.