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.

WeKruit/wekruit-pa

https://github.com/WeKruit/wekruit-pa · scanned 2026-06-16 00:57 UTC (2 months, 1 week ago)

740 raw signals (0 security + 740 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 709 actionable findings from 1 signal source. 31 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 · 709 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 52 Medium 99 Low 238 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 709 Crowd 0 Layer: Software 3 Frontend 56 Security 31 Cicd 1 Quality 554 Api 64

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 1 finding

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Legacy markers 17 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 `deferToLegacy` in tests/scenarios/prescreen/sim-le…
low Old/deprecated-named symbol `deferToLegacy` in apps/functions/src/index.ts:1331
low Old/deprecated-named symbol `v16_pool_failed_fallback_legacy` in apps/functions…
low Old/deprecated-named symbol `deferToLegacy` in apps/functions/src/__tests__/cla…
low Old/deprecated-named symbol `coresignal_collect_v2` in apps/functions/src/exter…
info Commented-code block (5 lines) in apps/functions/src/external-supply/legacy-use…
info Commented-code block (6 lines) in apps/functions/src/external-supply/legacy-use…
low Old/deprecated-named symbol `imessage_legacy` in apps/functions/src/sendblue/au…
low Old/deprecated-named symbol `deferToLegacy` in apps/functions/src/claire-agent/…
low Old/deprecated-named symbol `deferToLegacy` in apps/functions/src/claire-agent/…
low Old/deprecated-named symbol `deferToLegacy` in apps/functions/src/claire-agent/…
low Old/deprecated-named symbol `deferToLegacy` in apps/eval/thin-claire/repro-matc…

View all legacy markers findings →

Commented-out code 317 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 (5 lines) in tests/fixtures/v1.6-personas/__tests__/valida…
info Commented-code block (6 lines) in tests/scenarios/runner-local.mjs:81
info Commented-code block (5 lines) in tests/scenarios/seed-match-correctness.mjs:66
info Commented-code block (5 lines) in tests/scenarios/runner.mjs:66
info Commented-code block (5 lines) in tests/scenarios/entry-ux/s5-linkedin-oauth-pi…
info Commented-code block (5 lines) in tests/scenarios/lib/crisis-redteam-runner.mjs…
info Commented-code block (5 lines) in tests/scenarios/lib/voice-axes.mjs:177
info Commented-code block (9 lines) in tests/scenarios/lib/ab-injector-harness.mjs:2…
info Commented-code block (5 lines) in tests/scenarios/prescreen/sim-cross-session-s…
info Commented-code block (8 lines) in apps/recruiter-board-fn/src/recruiter-board.t…
info Commented-code block (5 lines) in apps/functions/build.mjs:137
info Commented-code block (5 lines) in apps/functions/scripts/e2e-bug-d-verify.mjs:3

View all commented-out code findings →

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

4 matching findings on this repo

low Stray `console.log` in TS/JS — packages/pa-orchestrator/src/voice/memory-policy…
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in apps/functions/src/claire-agent/prescreen-con…
info Commented-code block (6 lines) in apps/dashboard-web/vite.config.ts:7

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/db3724b6-50de-4425-9387-3fb54d17728d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/db3724b6-50de-4425-9387-3fb54d17728d/

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.