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

Scan timing: clone 3.86s · analysis 25.24s · 12.3 MB · GitHub preflight 532ms

xuzhougeng/wispterm

https://github.com/xuzhougeng/wispterm · scanned 2026-06-05 14:20 UTC (5 days, 5 hours ago) · 10 languages

258 raw signals (130 security + 128 graph) 32nd percentile · Typescript · medium (20-100K LoC) System graph score 80 (lower by 15)

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

Complete repo analysis

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

JSON
Combined
66.9
/100
Security checks
54
58 findings
System graph
80
88.9% cov · 36 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 32.9 0.25 8.22
testing_score 90.0 0.20 18.00
documentation_score 80.0 0.15 12.00
practices_score 71.0 0.15 10.65
code_quality 61.3 0.10 6.13
Overall 1.00 64.8
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 20 Medium 10 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 58 System graph 36 Crowd 0 Layer: Software 43 Cicd 8 Quality 33 Security 5 Api 1 Frontend 2 Hardware 2

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
  • medium GitHub Action `actions/configure-pages@v5` is 1 major version(s) behind (latest… .github/workflows/pages.yml:31
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/7084ae59-6326-4431-a8bd-10e406e46ecb/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/7084ae59-6326-4431-a8bd-10e406e46ecb/

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.