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.

WeCr8-Solutions/shift-handover-hub

https://github.com/WeCr8-Solutions/shift-handover-hub · scanned 2026-06-16 00:56 UTC (2 months, 1 week ago)

479 raw signals (77 security + 402 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 308 actionable findings from 2 signal sources. 354 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 · 301 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 7 Medium 87 Low 62 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 301 Crowd 0 Layer: Quality 78 Security 62 Frontend 160 Cicd 3 Api 5

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 16 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 scripts/prerender.mjs:39
info Commented-code block (6 lines) in desktop/src/main/setupWizard.ts:101
info Commented-code block (8 lines) in supabase/functions/send-transactional-email/i…
info Commented-code block (6 lines) in supabase/functions/issue-certificate/index.ts…
info Commented-code block (5 lines) in supabase/functions/send-email/index.ts:1
info Commented-code block (5 lines) in supabase/functions/sap-sync/index.ts:111
info Commented-code block (5 lines) in supabase/functions/log-export/index.ts:85
info Commented-code block (5 lines) in supabase/functions/create-cert-checkout/index…
info Commented-code block (5 lines) in supabase/functions/erp-sync/index.ts:146
info Commented-code block (5 lines) in supabase/functions/auth-email-hook/index.ts:43
info Commented-code block (5 lines) in public/oap/src/oap-engine.js:70
info Commented-code block (9 lines) in public/oap/src/oap-cert.js:1

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

medium Runtime service client appears to use placeholder configuration

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/0fc40876-2d58-41e8-b23c-be9bf36cb4b8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0fc40876-2d58-41e8-b23c-be9bf36cb4b8/

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.