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

Scan timing: clone 17.02s · analysis 2.17s · 26.3 MB · GitHub API rate-limit (preflight)

cloudwego/abcoder

https://github.com/cloudwego/abcoder · scanned 2026-05-31 01:23 UTC (5 days, 13 hours ago) · 10 languages

191 findings (67 legacy + 124 scanner) 11/13 scanners ran 100th percentile · Go · medium (20-100K LoC) Scanner says 65 (higher by 22)

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

Complete repo analysis

Last scanned 5 days, 13 hours ago · v2 · 129 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
77.7
/100
Repobility
91
67 legacy
9-layer
65
100.0% cov · 62 gaps
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 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 91.0 0.20 18.20
documentation_score 81.0 0.15 12.15
practices_score 72.0 0.15 10.80
code_quality 80.0 0.10 8.00
Overall 1.00 86.9
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 1 High 33 Medium 6 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 67 9-layer 62 Crowd 0 Layer: Software 33 Quality 55 Security 2 Frontend 13 Cicd 12 Api 14

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.

Fragile runtime 48 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium [COMP001] High cognitive complexity: Function `main` has cognitive complexity 1… script/diffjson.py:191
  • medium [COMP001] High cognitive complexity: Function `format_diff_custom` has cognitiv… script/diffjson.py:66
  • low [COMP001] High cognitive complexity: Function `process_directory_comparison` ha… script/diffjson.py:150
  • low [ERR003] Ignored Error (Go): Ignoring error return values. lang/utils/files.go:28
  • low [ERR003] Ignored Error (Go): Ignoring error return values. lang/lsp/lsp.go:168
  • low [SEC132] String concat where the language has interpolation (AI style drift): S… lang/java/pb/lib.go:140
  • low [ERR003] Ignored Error (Go): Ignoring error return values. lang/parse.go:70
  • low Duplicated implementation block across source files ts-parser/src/parser/VarParser.ts:384
  • low Duplicated implementation block across source files testdata/python/1_single/main.py:46
  • low Duplicated implementation block across source files testdata/python/1_single/main.py:15
  • low Duplicated implementation block across source files lang/utils/strings.go:40
  • low Duplicated implementation block across source files lang/utils/err.go:11
View all fragile runtime findings →
Config drift 5 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.
5 matching findings on this repo
  • low File has no detected symbols: ts-parser/jest.config.js
  • low File has no detected symbols: ts-parser/test-repo/src/config/app.config.ts
  • low File has no detected symbols: ts-parser/src/parser/test/jest.config.js
  • critical Possible secret in ts-parser/test-repo/src/config/app.config.ts ts-parser/test-repo/src/config/app.config.ts:45
  • low Unused endpoint: GET /api/config
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/db702b90-6668-4796-b198-40ebefc82950/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/db702b90-6668-4796-b198-40ebefc82950/

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.