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.

The-Focus-AI/umwelten

https://github.com/The-Focus-AI/umwelten · scanned 2026-06-16 00:33 UTC (2 months, 2 weeks ago)

253 raw signals (0 security + 253 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 239 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 65 Low 141 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 239 Crowd 0 Layer: Frontend 126 Hardware 6 Security 30 Cicd 4 Quality 73

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 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `unstable_legacy` in examples/umwelten-web-demo/pub…

View all legacy markers findings →

Commented-out code 27 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 packages/ui/src/tui/introspect/DashboardApp.t…
info Commented-code block (6 lines) in packages/ui/src/tui/introspect/dashboard/util…
info Commented-code block (5 lines) in packages/ui/src/tui/search/SessionSearchTui.t…
info Commented-code block (5 lines) in packages/evaluation/src/evaluation/suite.ts:3…
info Commented-code block (6 lines) in packages/evaluation/src/evaluation/strategies…
info Commented-code block (5 lines) in packages/sessions/src/introspect.ts:100
info Commented-code block (5 lines) in packages/core/src/cognition/usage-extractor.t…
info Commented-code block (6 lines) in packages/core/src/cognition/runner.ts:40
info Commented-code block (5 lines) in packages/core/src/cognition/usage-extractor.t…
info Commented-code block (6 lines) in packages/core/src/cognition/request-options.t…
info Commented-code block (5 lines) in packages/core/src/interaction/adapters/antigr…
info Commented-code block (6 lines) in packages/core/src/interaction/search/searcher…

View all commented-out code 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/53ba14a4-48a9-4311-88f8-e399a0dc53f4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/53ba14a4-48a9-4311-88f8-e399a0dc53f4/

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.