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.

Danwoltrs/WAQC

https://github.com/Danwoltrs/WAQC · scanned 2026-06-17 01:26 UTC (1 month, 2 weeks ago)

216 raw signals (0 security + 216 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -18.7 (diff) · 214 actionable findings from 1 signal source. 2 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 · 214 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 6 Medium 76 Low 68 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 214 Crowd 0 Layer: Api 1 Frontend 87 Security 17 Cicd 1 Quality 108

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 9 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.

9 matching findings on this repo

low Old/deprecated-named symbol `exporter_legacy` in src/app/cupping/page.tsx:51
low Old/deprecated-named symbol `exporter_legacy` in src/app/api/cupping/my-samples…
low Old/deprecated-named symbol `exporter_legacy` in src/app/api/samples/bulk-detai…
low Old/deprecated-named symbol `exporter_legacy` in src/app/grading/page.tsx:62
low Old/deprecated-named symbol `exporter_legacy` in src/app/sample-photo/[slug]/pa…
low Old/deprecated-named symbol `searchLegacy` in src/components/clients/add-client…
low Old/deprecated-named symbol `exporter_legacy` in src/components/cupping/print-c…
low Old/deprecated-named symbol `companies_with_legacy` in src/lib/qc-client-mapper…
low Old/deprecated-named symbol `companies_with_legacy` in src/lib/database.types.t…

View all legacy markers findings →

Commented-out code 21 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 src/app/api/clients/route.ts:16
info Commented-code block (5 lines) in src/app/api/cupping/scores/aggregate/route.ts…
info Commented-code block (5 lines) in src/app/api/notifications/samples-assigned/ro…
info Commented-code block (5 lines) in src/app/api/samples/route.ts:122
info Commented-code block (5 lines) in src/app/api/samples/[id]/duplicate/route.ts:1…
info Commented-code block (7 lines) in src/app/certificate/[slug]/page.tsx:94
info Commented-code block (5 lines) in src/app/samples/qc/page.tsx:962
info Commented-code block (7 lines) in src/components/clients/client-form.tsx:21
info Commented-code block (6 lines) in src/components/clients/client-quality-manager…
info Commented-code block (5 lines) in src/components/cupping/cupping-validation-mod…
info Commented-code block (5 lines) in src/components/cupping/cva/wheel/zoom-machine…
info Commented-code block (5 lines) in src/components/cupping/cva/wheel/FlavorWheel.…

View all commented-out code findings →

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

9 matching findings on this repo

medium Insecure pattern 'direct_innerhtml_assignment' in docs/prompts/qc-detail-config… docs/prompts/qc-detail-config-redesign.html:295
high Agent instruction/config may expose a secret: AGENTS.md AGENTS.md:67
high Agent instruction/config may expose a secret: GEMINI.md GEMINI.md:67
high Agent instruction/config may expose a secret: .github/instructions/taskmaster.i… .github/instructions/taskmaster.instructions.md:376
high Agent instruction/config may expose a secret: .cursor/rules/taskmaster/taskmast… .cursor/rules/taskmaster/taskmaster.mdc:377
high Agent instruction/config may expose a secret: .windsurf/rules/taskmaster.md .windsurf/rules/taskmaster.md:377
high Agent instruction/config may expose a secret: .claude/agents/task-checker.md .claude/agents/task-checker.md:13
medium `fetch()` without try/.catch or AbortSignal — src/components/clients/client-lab…
medium `fetch()` without try/.catch or AbortSignal — src/components/clients/qc-config-…

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/de84a732-6a01-412f-b0db-6b1cc198e235/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/de84a732-6a01-412f-b0db-6b1cc198e235/

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.