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.

wlsdks/Muse

https://github.com/wlsdks/Muse · scanned 2026-06-16 00:59 UTC (2 months, 1 week ago)

594 raw signals (0 security + 594 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 594 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 594 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 6 Medium 82 Low 108 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 594 Crowd 0 Layer: Frontend 4 Security 55 Quality 480 Api 55

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 `pb_legacy` in packages/autoconfigure/test/playbook…

View all legacy markers findings →

Commented-out code 396 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 apps/api/test/server.admin-session-compat.tes…
info Commented-code block (5 lines) in apps/api/test/p17-email-tool-agent-seam.test.…
info Commented-code block (7 lines) in apps/api/test/server.history.test.ts:94
info Commented-code block (8 lines) in apps/api/test/approval-round-trip-e2e.test.ts…
info Commented-code block (5 lines) in apps/api/test/server.accountability.test.ts:10
info Commented-code block (6 lines) in apps/api/src/compat-user-memory-store.test.ts…
info Commented-code block (6 lines) in apps/api/src/admin-routes.ts:68
info Commented-code block (6 lines) in apps/api/src/multi-agent-routes.ts:430
info Commented-code block (6 lines) in apps/api/src/consolidate-tick.ts:155
info Commented-code block (6 lines) in apps/api/src/chat-rate-limiter.ts:55
info Commented-code block (5 lines) in apps/api/src/voice-routes.ts:159
info Commented-code block (5 lines) in apps/api/src/compat-session-tag-store.test.ts…

View all commented-out code findings →

Config drift 39 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 Very large file: packages/autoconfigure/test/autoconfigure.test.ts (1301 lines)
low Very large file: packages/autoconfigure/src/index.ts (1218 lines)
low Node manifest has dependencies but no lockfile: packages/autoconfigure/package.… packages/autoconfigure/package.json
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in apps/cli/vitest.config.ts:3
info Commented-code block (5 lines) in packages/autoconfigure/test/dynamic-tool-regi…
info Commented-code block (6 lines) in packages/autoconfigure/test/mcp-stack-officia…
info Commented-code block (5 lines) in packages/autoconfigure/test/knowledge-recall-…
info Commented-code block (5 lines) in packages/autoconfigure/test/skills-runtime.te…
info Commented-code block (5 lines) in packages/autoconfigure/test/local-only-postur…
info Commented-code block (5 lines) in packages/autoconfigure/test/tasks-due-relevan…
info Commented-code block (8 lines) in packages/autoconfigure/test/autoconfigure.tes…

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/f29698de-a3d7-4c1f-8403-d0cdd611fac9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f29698de-a3d7-4c1f-8403-d0cdd611fac9/

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.