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.

Ricou-IA/majordhome

https://github.com/Ricou-IA/majordhome · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

163 raw signals (3 security + 160 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 160 actionable findings from 2 signal sources. 3 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 · 157 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 4 Medium 36 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 157 Crowd 0 Layer: Quality 77 Frontend 71 Security 10 Cicd 2

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

3 matching findings on this repo

low Old/deprecated-named symbol `appointment_legacy` in src/apps/artisan/components…
low Old/deprecated-named symbol `appointment_legacy` in src/apps/artisan/components…
low Old/deprecated-named symbol `appointment_legacy` in src/shared/services/clients…

View all legacy markers findings →

Commented-out code 36 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 vite.config.js:14
info Commented-code block (7 lines) in supabase/functions/resend-webhook/index.ts:8
info Commented-code block (5 lines) in supabase/functions/mailing-scheduler/index.ts…
info Commented-code block (6 lines) in supabase/functions/voice-extract-fieldreport/…
info Commented-code block (9 lines) in supabase/functions/pennylane-proxy/index.ts:13
info Commented-code block (5 lines) in supabase/functions/pennylane-sync-cron/index.…
info Commented-code block (7 lines) in supabase/functions/mailing-unsubscribe/index.…
info Commented-code block (6 lines) in supabase/functions/resend-domain-onboard/inde…
info Commented-code block (10 lines) in supabase/functions/contract-signed-notify/in…
info Commented-code block (19 lines) in supabase/functions/mailing-send/index.ts:1
info Commented-code block (5 lines) in supabase/functions/gsc-sync/index.ts:9
info Commented-code block (6 lines) in supabase/functions/pennylane-sync-quote-statu…

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

high Agent instruction/config may expose a secret: .claude/proposed-updates.md .claude/proposed-updates.md:375
high Agent instruction/config may expose a secret: .claude/settings.local.json .claude/settings.local.json:91
info Commented-code block (5 lines) in vite.config.js:14

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/3bdd3b65-1f62-4d45-b6da-3ddb8f9f9ba4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3bdd3b65-1f62-4d45-b6da-3ddb8f9f9ba4/

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.