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.

zudolab/zudo-doc

https://github.com/zudolab/zudo-doc · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

331 raw signals (0 security + 331 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 327 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 66 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 327 Crowd 0 Layer: Api 1 Frontend 43 Security 27 Cicd 2 Quality 254

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.

Commented-out code 231 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 (10 lines) in playwright.config.ts:44
info Commented-code block (8 lines) in zfb-shim.d.ts:3
info Commented-code block (11 lines) in zfb.config.ts:143
info Commented-code block (8 lines) in vitest.config.ts:8
info Commented-code block (12 lines) in scripts/check-pin-parity.mjs:10
info Commented-code block (6 lines) in scripts/check-b4push-ci-parity.mjs:7
info Commented-code block (5 lines) in scripts/dev-claude-watch.mjs:103
info Commented-code block (5 lines) in scripts/release-bootstrap-latest.mjs:7
info Commented-code block (11 lines) in scripts/report-retry-flakes.mjs:18
info Commented-code block (5 lines) in scripts/check-links.js:211
info Commented-code block (7 lines) in scripts/check-package-safelist.mjs:8
info Commented-code block (5 lines) in scripts/check-e2e-spec-naming.mjs:13

View all commented-out code findings →

Config drift 13 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 Commented-code block (10 lines) in playwright.config.ts:44
info Commented-code block (11 lines) in zfb.config.ts:143
info Commented-code block (8 lines) in vitest.config.ts:8
info Commented-code block (5 lines) in packages/create-zudo-doc/templates/base/src/c…
info Commented-code block (5 lines) in packages/create-zudo-doc/templates/base/src/c…
info Commented-code block (5 lines) in packages/create-zudo-doc/templates/base/src/c…
info Commented-code block (6 lines) in packages/create-zudo-doc/src/zfb-config-gen.t…
info Commented-code block (9 lines) in packages/create-zudo-doc/src/__tests__/zfb-co…
info Commented-code block (10 lines) in packages/zudo-doc/tsup.config.ts:3
info Commented-code block (7 lines) in packages/zudo-doc/vitest.config.ts:56
info Commented-code block (5 lines) in src/config/z-index-tokens.ts:3
info Commented-code block (5 lines) in src/config/docs-schema.ts:69

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/16aa1433-738a-4606-b1e1-23123a0a619c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/16aa1433-738a-4606-b1e1-23123a0a619c/

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.