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.

Zoo-Code-Org/Zoo-Code

https://github.com/Zoo-Code-Org/Zoo-Code · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

318 raw signals (0 security + 318 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 318 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 1 Medium 60 Low 143 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 318 Crowd 0 Layer: Frontend 142 Security 46 Cicd 3 Quality 127

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 `executeLegacy` in src/core/tools/ReadFileTool.ts:77

View all legacy markers findings →

Commented-out code 65 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/cli/src/ui/App.tsx:303
info Commented-code block (7 lines) in apps/vscode-e2e/src/runTest.ts:120
info Commented-code block (5 lines) in apps/vscode-e2e/src/bedrock-mock-server.ts:12
info Commented-code block (5 lines) in apps/vscode-e2e/src/suite/mcp-oauth.test.ts:1…
info Commented-code block (7 lines) in apps/vscode-e2e/src/suite/providers/bedrock.t…
info Commented-code block (7 lines) in apps/vscode-e2e/src/suite/providers/zai.test.…
info Commented-code block (5 lines) in packages/types/src/tool-params.ts:92
info Commented-code block (6 lines) in packages/types/src/utils/looksLikeFilePath.ts…
info Commented-code block (10 lines) in packages/types/src/providers/bedrock.ts:600
info Commented-code block (7 lines) in packages/types/src/providers/openrouter.ts:59
info Commented-code block (5 lines) in webview-ui/src/__tests__/ContextWindowProgres…
info Commented-code block (5 lines) in webview-ui/src/utils/removeLeadingNonAlphanum…

View all commented-out code findings →

Config drift 16 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

info TODO/FIXME marker in shipping code — webview-ui/vite.config.ts:71
low Stray `console.log` in TS/JS — webview-ui/vite.config.ts:46
info `truncate` class without `title=` for hover reveal — webview-ui/src/components/…
info TODO/FIXME marker in shipping code — src/core/config/ProviderSettingsManager.ts…
low Stray `console.log` in TS/JS — src/core/config/ProviderSettingsManager.ts:310
info TODO/FIXME marker in shipping code — src/core/config/importExport.ts:237
medium Insecure pattern 'node_child_process' in webview-ui/vite.config.ts:3 webview-ui/vite.config.ts:3
medium Insecure pattern 'cors_wildcard' in webview-ui/vite.config.ts:144 webview-ui/vite.config.ts:144
critical Possible secret in src/core/config/__tests__/ProviderSettingsManager.spec.ts src/core/config/__tests__/ProviderSettingsManager…:591
critical Possible secret in src/core/config/__tests__/ContextProxy.spec.ts src/core/config/__tests__/ContextProxy.spec.ts:547
low Very large file: src/services/code-index/__tests__/config-manager.spec.ts (2035…
low Very large file: src/core/config/__tests__/CustomModesManager.spec.ts (1760 lin…

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/1226948b-e1d5-4696-ade9-6034e1c8613c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1226948b-e1d5-4696-ade9-6034e1c8613c/

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.