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.

avakero/zukai-prompt-builder

https://github.com/avakero/zukai-prompt-builder · scanned 2026-06-17 01:36 UTC (1 month, 2 weeks ago)

55 raw signals (0 security + 55 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -8.4 (diff) · 55 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 55 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 25 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 55 Crowd 0 Layer: Frontend 7 Security 12 Cicd 1 Quality 35

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 13 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 (8 lines) in app.js:98
info Commented-code block (7 lines) in build-wp.js:52
info Commented-code block (10 lines) in api/straico.js:1
info Commented-code block (8 lines) in api/upload-character-image.js:1
info Commented-code block (5 lines) in api/gemini-image.js:5
info Commented-code block (13 lines) in api/pickaxe-proxy.js:1
info Commented-code block (11 lines) in api/me.js:1
info Commented-code block (7 lines) in api/log-slide.js:13
info Commented-code block (13 lines) in api/job.js:1
info Commented-code block (5 lines) in api/cleanup-storage.js:3
info Commented-code block (9 lines) in api/log-generation.js:5
info Commented-code block (5 lines) in api/openai-image.js:5

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

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/skills/security-review/cl… .claude/skills/security-review/cloud-infrastructu…:33
high Agent instruction/config may expose a secret: .claude/skills/security-review/SK… .claude/skills/security-review/SKILL.md:27
high Agent instruction/config may expose a secret: .claude/skills/deployment-pattern… .claude/skills/deployment-patterns/SKILL.md:337
high Agent instruction/config may expose a secret: .claude/skills/backend-patterns/S… .claude/skills/backend-patterns/SKILL.md:107
high Agent instruction/config may expose a secret: .claude/skills/api-design/SKILL.md .claude/skills/api-design/SKILL.md:306

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/5b14d429-3d97-4fa6-a47e-a6dfb05c3246/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5b14d429-3d97-4fa6-a47e-a6dfb05c3246/

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.