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.

Djembo31/beScout-App

https://github.com/Djembo31/beScout-App · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

409 raw signals (0 security + 409 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 26 High 2 Medium 78 Low 113 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 399 Crowd 0 Layer: Software 3 Api 1 Frontend 193 Security 38 Cicd 2 Quality 162

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 70 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 scripts/backfill-scoring-historical.mjs:527
info Commented-code block (7 lines) in scripts/type-truth-audit.ts:100
info Commented-code block (5 lines) in scripts/silent-fail-audit.ts:64
info Commented-code block (7 lines) in scripts/beta-metrics.mjs:2
info Commented-code block (6 lines) in scripts/wiring-check.ts:63
info Commented-code block (5 lines) in scripts/cron-health-check.ts:143
info Commented-code block (5 lines) in scripts/archived/2026-04-28-once-off/tm-squad…
info Commented-code block (10 lines) in src/app/api/cron/live-score-sync/route.ts:100
info Commented-code block (7 lines) in src/app/api/cron/gameweek-sync/route.ts:725
info Commented-code block (5 lines) in src/app/api/admin/sync-contracts/route.ts:86
info Commented-code block (5 lines) in src/app/api/players/route.ts:61
info Commented-code block (5 lines) in src/app/(app)/layout.tsx:49

View all commented-out code findings →

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

3 matching findings on this repo

critical Possible secret in e2e/bots/bot-config.ts e2e/bots/bot-config.ts:6
high Agent instruction/config may expose a secret: .claude/commands/security-best-pr… .claude/commands/security-best-practices.md:15
high Agent instruction/config may expose a secret: .claude/rules/errors-db.md .claude/rules/errors-db.md:431

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/85eb7069-5fda-4457-bb80-402b1480dee5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/85eb7069-5fda-4457-bb80-402b1480dee5/

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.