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.

utopusc/livinity-io

https://github.com/utopusc/livinity-io · scanned 2026-06-16 00:47 UTC (2 months, 1 week ago)

1148 raw signals (0 security + 1148 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 1109 actionable findings from 1 signal source. 39 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 · 1109 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 9 High 103 Medium 167 Low 204 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1109 Crowd 0 Layer: Frontend 214 Network 6 Hardware 9 Security 104 Cicd 5 Quality 629 Api 142

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

10 matching findings on this repo

info TODO/FIXME marker in shipping code — livos/packages/livinityd/source/modules/ap…
critical Possible secret in livos/packages/livinityd/source/modules/apps/legacy-compat/a… livos/packages/livinityd/source/modules/apps/lega…:31
critical Possible secret in livos/packages/livinityd/source/modules/apps/legacy-compat/a… livos/packages/livinityd/source/modules/apps/lega…:32
low Old/deprecated-named symbol `withLegacy` in liv/packages/core/src/api.scope-fil…
low Old/deprecated-named symbol `exposeLegacy` in liv/packages/core/src/agent-sessi…
low Old/deprecated-named symbol `sheetOpenLegacy` in livos/packages/ui/src/modules/…
low Old/deprecated-named symbol `verifyLegacy` in livos/packages/livinityd/source/m…
low Old/deprecated-named symbol `ListWindowsLegacy` in livos/packages/livinityd/sou…
low Old/deprecated-named symbol `seedLegacy` in livos/packages/livinityd/source/mod…
low Old/deprecated-named symbol `msg_legacy` in livos/packages/livinityd/source/mod…

View all legacy markers findings →

Commented-out code 524 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 (5 lines) in docker/local-uat/uat-driver/walk.mjs:1
info Commented-code block (6 lines) in docker/local-uat/uat-driver/lib/chrome-cdp.mj…
info Commented-code block (5 lines) in docker/local-uat/uat-driver/lib/tcpdump-check…
info Commented-code block (7 lines) in scripts/aionui-patches/install-liv-mcps-secti…
info Commented-code block (6 lines) in scripts/aionui-patches/local-agents-install-s…
info Commented-code block (5 lines) in platform/relay/src/index.ts:432
info Commented-code block (5 lines) in platform/relay/src/admin-tunnel.test.ts:183
info Commented-code block (5 lines) in platform/relay/src/server.ts:209
info Commented-code block (6 lines) in platform/relay/src/subdomain-parser.ts:50
info Commented-code block (5 lines) in platform/web/next.config.ts:7
info Commented-code block (7 lines) in platform/web/scripts/poc-presence.mjs:1
info Commented-code block (7 lines) in platform/web/public/tweaks-panel.jsx:12

View all commented-out code findings →

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

12 matching findings on this repo

low Stray `console.log` in TS/JS — livos/packages/ui/stories/vite.config.ts:10
low Stray `console.log` in TS/JS — livos/packages/cli/src/commands/config.ts:22
low Node manifest has dependencies but no lockfile: livos/packages/config/package.j… livos/packages/config/package.json
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/skills/luse/ANTI-PATTERNS… .claude/skills/luse/ANTI-PATTERNS.md:123
info Commented-code block (5 lines) in platform/web/next.config.ts:7
info Commented-code block (5 lines) in livos/packages/ui/playwright.config.ts:72
info Commented-code block (13 lines) in livos/packages/ui/vite.config.ts:42
info Commented-code block (7 lines) in livos/packages/ui/tailwind.config.ts:12
info Commented-code block (5 lines) in livos/packages/livinityd/source/modules/serve…
info Commented-code block (5 lines) in livos/packages/livinityd/source/modules/serve…
info Commented-code block (6 lines) in livos/packages/livinityd/source/modules/serve…

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/6e640f61-1e00-4438-8d00-f3f960c01e44/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6e640f61-1e00-4438-8d00-f3f960c01e44/

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.