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.

likec4/likec4

https://github.com/likec4/likec4 · scanned 2026-07-23 19:40 UTC (4 days, 21 hours ago)

228 raw signals (0 security + 228 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v7 · last Δ +10.1 (diff) · 211 actionable findings from 1 signal source. 17 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 · 211 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 31 Medium 70 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 211 Crowd 0 Layer: Frontend 38 Security 71 Quality 45 Hardware 3 Cicd 5 Dependencies 48 Api 1

Exclude dismissed / FP Exclude test files

Last 7 scans of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

Jul 23 05:29

Jul 23 05:53

Jul 23 07:34

Jul 23 08:24

Jul 23 10:36

Jul 23 18:42

Jul 23 19:39

Diff: previous → latest scan

Score Δ

10.10

Gaps added

Gaps resolved

Edges changed

+1 / -1

New gaps in latest scan:

Debug logging residue appears in source files low
Placeholder or mock-heavy implementation detected medium
Critical user flow still appears backed by mock or placeholder data medium
Agent instructions exist but release-hardening basics are missing medium
Commented-code block (11 lines) in packages/vscode/src/useMessenger.ts:178 info
+ 2 more

Gaps resolved since last scan:

Debug logging residue appears in source files
Placeholder or mock-heavy implementation detected
Critical user flow still appears backed by mock or placeholder data
Agent instructions exist but release-hardening basics are missing
Commented-code block (5 lines) in styled-system/preset/src/globalCss.ts:56

v#	ID	Status	Score	Gaps	Nodes	Commit	Started
v	`scan_task_515a544d4a2068e115b42b5575b04f25`	ok	64.2	228	33896	`f970062` v1.59.2	Jul 23 19:39
v	`scan_task_0104110bca32b5e43665ef7c1613c6a9`	ok	54.1	266	33896	`f970062` v1.59.2	Jul 23 18:42
v	`scan_task_a6bb37f0ecea11ed6a932594b4597abd`	ok	54.0	302	33896	`f970062` v1.59.2	Jul 23 10:36
v	`scan_7e4ff6fc49b7`	ok	54.3	335	33896	`f970062` v1.59.2	Jul 23 08:24
v	`scan_3aca05269b67`	ok	49.9	317	33040	`f970062` v1.59.2	Jul 23 07:34
v	`scan_066537d0143e`	ok	49.9	322	33040	`f970062` v1.59.2	Jul 23 05:53
v	`scan_35ef3338f620`	failed	—	—	—	—	Jul 23 05:29

Recent failures

scan_35ef3338f620 — 5 days, 11 hours ago

clone failed: git clone failed for https://github.com/likec4/likec4: fatal: unable to access 'https://github.com/likec4/likec4/': Could not resolve host: github.com

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/f231e8af-e109-4b5e-ae83-0e556bc3197f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f231e8af-e109-4b5e-ae83-0e556bc3197f/

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.