karenrlacour-collab/luminapost-elite

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.

Scan timing: clone 1.28s · analysis 1.36s · 0.5 MB · GitHub API rate-limit (preflight)

https://github.com/karenrlacour-collab/luminapost-elite.git · scanned 2026-05-25 16:20 UTC (1 week, 3 days ago) · 10 languages

118 findings (24 legacy + 94 scanner) 3rd percentile · Typescript · small (2-20K LoC) Scanner says 67 (lower by 22)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 71 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	63.6	0.25	15.90
`testing_score`	0.0	0.20	0.00
`documentation_score`	0.0	0.15	0.00
`practices_score`	40.0	0.15	6.00
`code_quality`	77.9	0.10	7.79
Overall		1.00	44.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 4 Medium 11 Low 43 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 24 9-layer 47 Crowd 0 Layer: Quality 20 Security 8 Software 38 Api 1 Frontend 2 Data 1 Cicd 1

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.

Fragile runtime 14 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium Public web service has no security.txt .well-known/security.txt
medium Public web app has no Content Security Policy index.html
medium Parallel implementation file sits beside a canonical file src/routes/admin.articles.new.tsx:1
low robots.txt does not advertise a sitemap public/robots.txt
low Public web app has no humans.txt humans.txt
low Duplicate top-level symbol appears in a patch-style file src/routes/admin.articles.new.tsx:1
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/integrations/supabase/client.ts:17
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/integrations/supabase/client.server.ts:18
info [MINED044] Js Console Log Prod: console.log left in code. Should be replaced wi… src/integrations/supabase/auth-middleware.ts:21
info [MINED058] React Dangerously Set Html: dangerouslySetInnerHTML bypasses Reacts … src/routes/article.$slug.tsx:100
info [MINED058] React Dangerously Set Html: dangerouslySetInnerHTML bypasses Reacts … src/components/ui/chart.tsx:73
info [MINED056] React Key As Index: key={index} in map() — re-renders the wrong elem… src/routes/about.tsx:91

View all fragile runtime findings →

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (6 lines) in vite.config.ts:1

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 No CI/CD configuration found
low File has no detected symbols: vite.config.ts
low File has no detected symbols: eslint.config.js
info Commented-code block (6 lines) in vite.config.ts:1

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/6309549d-7da0-4fbd-99ea-56f06c1cc8a9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6309549d-7da0-4fbd-99ea-56f06c1cc8a9/

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.