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.

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

Scan timing: clone 19.95s · analysis 4.28s · 46.2 MB · GitHub API rate-limit (preflight)

013677890/LCchat-Backend

https://github.com/013677890/LCchat-Backend · scanned 2026-06-16 03:37 UTC (2 months ago) · 10 languages

139 raw signals (122 security + 17 graph) 11/13 scanners ran 67th percentile · Go · medium (20-100K LoC) System graph score 82 (lower by 5)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months ago · v1 · 74 actionable findings from 2 signal sources. 65 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 17 findings

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`	84.0	0.20	16.80
`documentation_score`	47.0	0.15	7.05
`practices_score`	54.0	0.15	8.10
`code_quality`	78.0	0.10	7.80
Overall		1.00	77.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 1 High 29 Medium 9 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 57 System graph 17 Crowd 0 Layer: Quality 30 Security 30 Cicd 9 Software 1 Hardware 3 Frontend 1

Exclude dismissed / FP Exclude test files

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

Possible secret in docker-compose.yml

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 docker-compose.yml:136; move to env var / secrets manager.

docker-compose.yml:136

Dockerfile runs as root: Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

No CI/CD pipelines detected

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

Placeholder or mock-heavy implementation detected

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

Critical user flow still appears backed by mock or placeholder data

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

Agent instructions exist but release-hardening basics are missing

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

Near-duplicate function bodies in 2 places

GapSeverity.LOW Layer.QUALITY score 0.113

Why: low severity · crashes are likely without this

Fix: Add a timeout on the call and wrap the body in this language’s exception-handling primitive.

Docker base image is tag-pinned but not digest-pinned: golang:1.25-alpine

GapSeverity.LOW Layer.HARDWARE score 0.100

Why: low severity

Dockerfile:1

Docker base image is tag-pinned but not digest-pinned: alpine:3.21

GapSeverity.LOW Layer.HARDWARE score 0.100

Why: low severity

Dockerfile:26

#10

Very large file: apps/group/internal/repository/group_repository.go (2026 lines)

GapSeverity.LOW Layer.QUALITY score 0.100

Why: low severity

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/d8c38c70-439c-420c-848b-27b4a69a486b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d8c38c70-439c-420c-848b-27b4a69a486b/

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.