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.

u7404677510-pixel/Monjoel_v1

https://github.com/u7404677510-pixel/Monjoel_v1 · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

100 raw signals (0 security + 100 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 100 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 100 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 34 Low 24 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 100 Crowd 0 Layer: Api 1 Frontend 50 Security 11 Cicd 1 Quality 37

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 13 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 (9 lines) in eslint.config.mjs:16
info Commented-code block (6 lines) in next.config.mjs:137
info Commented-code block (5 lines) in scripts/compress-images.mjs:197
info Commented-code block (6 lines) in components/sections/HeroCinematic.tsx:325
info Commented-code block (5 lines) in components/sections/CoverageMap.tsx:63
info Commented-code block (6 lines) in components/hero/JoelWordmark.tsx:408
info Commented-code block (7 lines) in app/sitemap.ts:172
info Commented-code block (6 lines) in app/api/contact/route.ts:42
info Commented-code block (5 lines) in lib/supabase.ts:23
info Commented-code block (5 lines) in lib/seo/search-index.ts:193
info Commented-code block (5 lines) in lib/seo/premium/schema.ts:187
info Commented-code block (6 lines) in lib/seo/premium/contextualLinks.ts:172

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

medium Runtime service client appears to use placeholder configuration
medium CI is configured but no tests are detected
info Commented-code block (9 lines) in eslint.config.mjs:16
info Commented-code block (6 lines) in next.config.mjs:137

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/e43603e0-9397-4efc-b006-15a25596ee0f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e43603e0-9397-4efc-b006-15a25596ee0f/

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.