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

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.

Legacy markers 3 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

3 matching findings on this repo

info TODO/FIXME marker in shipping code — packages/core/src/compute-view/element-vie… packages/core/src/compute-view/element-view/__tes…:64
low Old/deprecated-named symbol `cloud_legacy` in e2e/src/likec4-model.test-d.ts:72
low Old/deprecated-named symbol `cloud_legacy` in e2e/src/likec4-views.test-d.ts:79

View all legacy markers findings →

Commented-out code 15 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in apps/playground/worker/types.ts:56 apps/playground/worker/types.ts:56
info Commented-code block (11 lines) in packages/vscode/src/useMessenger.ts:178 packages/vscode/src/useMessenger.ts:178
info Commented-code block (9 lines) in packages/diagram/src/search/components/styles… packages/diagram/src/search/components/styles.css…:50
info Commented-code block (5 lines) in packages/diagram/src/likec4diagram/state/util… packages/diagram/src/likec4diagram/state/utils.ts:93
info Commented-code block (5 lines) in packages/core/src/model/connection/ops.ts:258 packages/core/src/model/connection/ops.ts:258
info Commented-code block (11 lines) in packages/core/src/compute-view/element-view/… packages/core/src/compute-view/element-view/clean…:27
info Commented-code block (6 lines) in packages/core/src/compute-view/deployment-vie… packages/core/src/compute-view/deployment-view/pr…:27
info Commented-code block (6 lines) in packages/core/src/compute-view/deployment-vie… packages/core/src/compute-view/deployment-view/pr…:80
info Commented-code block (6 lines) in packages/core/src/compute-view/deployment-vie… packages/core/src/compute-view/deployment-view/pr…:74
info Commented-code block (5 lines) in packages/core/src/compute-view/deployment-vie… packages/core/src/compute-view/deployment-view/st…:38
info Commented-code block (9 lines) in packages/core/src/compute-view/relationships-… packages/core/src/compute-view/relationships-view…:61
info Commented-code block (11 lines) in packages/language-server/src/validation/impo… packages/language-server/src/validation/imports.ts:32

View all commented-out code findings →

Config drift 2 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.

2 matching findings on this repo

high Insecure pattern 'node_child_process' in packages/diagram/vite.config.ts:3 packages/diagram/vite.config.ts:3
low Node manifest has dependencies but no lockfile: packages/config/package.json packages/config/package.json

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