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.

zuplo/zudoku

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

165 raw signals (0 security + 165 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 151 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 · 151 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 19 Medium 35 Low 58 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 151 Crowd 0 Layer: Frontend 42 Security 8 Cicd 3 Quality 77 Api 21

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 14 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 (7 lines) in docs/sidebar.ts:17
info Commented-code block (6 lines) in packages/create-zudoku/templates/zuplo/zudoku…
info Commented-code block (5 lines) in packages/zudoku/src/config/loader.ts:247
info Commented-code block (7 lines) in packages/zudoku/src/cli/common/analytics/lib.…
info Commented-code block (5 lines) in packages/zudoku/src/vite/mdx/remark-link-rewr…
info Commented-code block (8 lines) in packages/zudoku/src/lib/util/joinUrl.test.ts:…
info Commented-code block (5 lines) in packages/zudoku/src/lib/components/Markdown.t…
info Commented-code block (5 lines) in packages/zudoku/src/lib/components/navigation…
info Commented-code block (6 lines) in packages/plugin-zuplo-monetization/src/utils/…
info Commented-code block (5 lines) in packages/plugin-zuplo-monetization/src/utils/…
info Commented-code block (8 lines) in packages/plugin-zuplo-monetization/src/utils/…
info Commented-code block (7 lines) in packages/plugin-zuplo-monetization/src/pages/…

View all commented-out code findings →

Config drift 6 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.

6 matching findings on this repo

low Stray `console.log` in TS/JS — packages/zudoku/src/config/validators/ZudokuConf…
low Node manifest has dependencies but no lockfile: examples/with-vite-config/packa… examples/with-vite-config/package.json
low Node manifest has dependencies but no lockfile: examples/with-config/package.js… examples/with-config/package.json
medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in packages/create-zudoku/templates/zuplo/zudoku…
info Commented-code block (5 lines) in packages/zudoku/src/config/loader.ts:247

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/555a956c-836c-409c-83ee-42d751367b63/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/555a956c-836c-409c-83ee-42d751367b63/

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.