zts212653/clowder-ai

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.

112 of your 194 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 102.95s for a 115.3 MB repo slow.
Repobility's analysis ran in 29.69s after the clone landed.

https://github.com/zts212653/clowder-ai · scanned 2026-06-05 19:55 UTC (4 days, 15 hours ago) · 10 languages

1462 raw signals (174 security + 1288 graph) 11/13 scanners ran 68th percentile · Typescript · huge (>500K LoC) System graph score 59 (higher by 28)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 15 hours ago · v2 · 712 actionable findings from 2 signal sources. 106 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 · 629 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	95.0	0.20	19.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	84.0	0.15	12.60
`code_quality`	69.0	0.10	6.90
Overall		1.00	87.5

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 76 Medium 52 Low 241 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 83 System graph 629 Crowd 0 Layer: Software 59 Quality 430 Security 29 Cicd 4 Frontend 118 Network 2 Api 70

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 6 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 18 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.

12 matching findings on this repo

low Old/deprecated-named symbol `unrelated_legacy` in packages/api/test/antigravity…
low Old/deprecated-named symbol `oci_group_legacy` in packages/api/test/dingtalk-ad…
low Old/deprecated-named symbol `migrateLegacy` in packages/api/test/capability-orc…
low Old/deprecated-named symbol `catCafeLegacy` in packages/api/test/f041-integrati…
low Old/deprecated-named symbol `disabledLegacy` in packages/api/test/harness-eval/…
low Old/deprecated-named symbol `trusted_legacy` in packages/api/test/memory/f163-h…
low Old/deprecated-named symbol `trusted_legacy` in packages/api/test/memory/f188-v…
low Old/deprecated-named symbol `trusted_legacy` in packages/api/test/memory/f188-l…
low Old/deprecated-named symbol `trusted_legacy` in packages/api/test/memory/f188-v…
low Old/deprecated-named symbol `migratedProjectLegacy` in packages/api/src/config/…
low Old/deprecated-named symbol `phaseWasLegacy` in packages/api/src/routes/callbac…
low Old/deprecated-named symbol `enabledLegacy` in packages/api/src/infrastructure/…

View all legacy markers findings →

Commented-out code 234 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 (9 lines) in scripts/services/llm-postprocess-api.py:30
info Commented-code block (5 lines) in scripts/services/embed-api.py:315
info Commented-code block (5 lines) in desktop/afterPack.js:32
info Commented-code block (7 lines) in desktop/service-manager.js:183
info Commented-code block (5 lines) in packages/api/test/f194-canonical-liveness-que…
info Commented-code block (5 lines) in packages/api/test/rules-route.test.js:103
info Commented-code block (5 lines) in packages/api/test/antigravity-bridge-session.…
info Commented-code block (5 lines) in packages/api/test/codex-agent-service.test.js…
info Commented-code block (5 lines) in packages/api/test/callback-auth-debug-route.t…
info Commented-code block (5 lines) in packages/api/test/reconcileZombies.test.js:123
info Commented-code block (5 lines) in packages/api/test/env-registry.test.js:286
info Commented-code block (6 lines) in packages/api/test/f194-canonical-liveness-rou…

View all commented-out code findings →

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

high [MINED113] Express PUT /api/config/default-cat has no auth: Express route PUT /… packages/api/src/routes/config.ts:419
high [MINED113] Express PATCH /api/config/env has no auth: Express route PATCH /api/… packages/api/src/routes/config.ts:294
high [MINED113] Express PATCH /api/config/owner has no auth: Express route PATCH /ap… packages/api/src/routes/config.ts:263
high [MINED113] Express PATCH /api/config/co-creator has no auth: Express route PATC… packages/api/src/routes/config.ts:260
high [MINED113] Express PATCH /api/config has no auth: Express route PATCH /api/conf… packages/api/src/routes/config.ts:162
low Very large file: packages/api/test/mcp-config-adapters.test.js (1616 lines)
low Very large file: packages/api/test/cat-config-loader.test.js (1597 lines)
low Very large file: packages/api/src/config/env-registry.ts (1842 lines)
low Very large file: packages/api/src/config/capabilities/capability-orchestrator.t…
info Commented-code block (5 lines) in packages/api/test/mcp-config-adapters.test.js…
info Commented-code block (9 lines) in packages/api/src/config/account-resolver.ts:3…
info Commented-code block (5 lines) in packages/api/src/config/session-strategy.ts:57

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/5b66fd59-9503-4ef3-990f-ff5ca22a2c7d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5b66fd59-9503-4ef3-990f-ff5ca22a2c7d/

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.