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.

sbreppez/MOVESBOOK-dev

https://github.com/sbreppez/MOVESBOOK-dev · scanned 2026-06-16 00:03 UTC (2 months, 3 weeks ago)

80 raw signals (0 security + 80 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 73 actionable findings from 1 signal source. 7 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 · 73 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 0 Medium 17 Low 28 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 73 Crowd 0 Layer: Frontend 10 Security 16 Cicd 1 Quality 46

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

2 matching findings on this repo

low Old/deprecated-named symbol `ph_legacy` in src/components/train/battlePrepHelpe…
low Old/deprecated-named symbol `isLegacy` in src/components/train/GoalModal.jsx:31

View all legacy markers findings →

Commented-out code 18 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 (10 lines) in functions/index.js:14
info Commented-code block (5 lines) in src/App.jsx:325
info Commented-code block (6 lines) in src/constants/textStreamCategories.js:128
info Commented-code block (7 lines) in src/utils/textStream.js:260
info Commented-code block (5 lines) in src/utils/textStreamWraps.js:63
info Commented-code block (6 lines) in src/utils/reportEngine.js:306
info Commented-code block (5 lines) in src/components/shared/ArcVis.jsx:80
info Commented-code block (6 lines) in src/components/shared/ErrorBoundary.jsx:4
info Commented-code block (6 lines) in src/components/home/DaySections.jsx:138
info Commented-code block (5 lines) in src/components/moves/WIPPage.jsx:142
info Commented-code block (14 lines) in src/components/moves/MoveRow.jsx:11
info Commented-code block (6 lines) in src/components/moves/map/ToTryListView.jsx:8

View all commented-out code findings →

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

2 matching findings on this repo

critical Possible secret in index-dev_v1_firestore_config.html index-dev_v1_firestore_config.html:39
medium Insecure pattern 'direct_innerhtml_assignment' in index-dev_v1_firestore_config… index-dev_v1_firestore_config.html:111

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/981f258d-683f-483e-a0c6-aeca7a55c26f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/981f258d-683f-483e-a0c6-aeca7a55c26f/

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.