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

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

#1
Possible secret in ts-parser/test-repo/src/config/app.config.ts
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 ts-parser/test-repo/src/config/app.config.ts:45; move to env var / secrets manager.
ts-parser/test-repo/src/config/app.config.ts:45
#2
Dangling fetch: GET https://api.example.com/data (ts-parser/test-repo/src/services/ExportDefault.ts:4)
GapSeverity.HIGH Layer.API score 0.338
Why: high severity · contract mismatch FE↔BE
Fix: Confirm the FE call URL matches a backend endpoint; update one side.
#3
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/pr-check.yml:12
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/go-test.yml:39
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/regression.yml:46
#6
`fetch()` without try/.catch or AbortSignal — ts-parser/test-repo/src/services/ExportDefault.ts:4
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in ts-parser/test-repo/src/services/ExportDefault.ts:4, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#7
Stray `console.log` in TS/JS — ts-parser/test-repo/src/test-export-default.ts:3
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in ts-parser/test-repo/src/test-export-default.ts:3.
#8
Stray `console.log` in TS/JS — ts-parser/test-repo/src/middleware/Test.ts:2
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in ts-parser/test-repo/src/middleware/Test.ts:2.
#9
Stray `console.log` in TS/JS — ts-parser/test-repo/src/utils/Logger.ts:10
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in ts-parser/test-repo/src/utils/Logger.ts:10.
#10
Stray `console.log` in TS/JS — ts-parser/src/index.ts:35
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in ts-parser/src/index.ts:35.

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/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.