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.

YohanRVVNexbu/camalmusalem

https://github.com/YohanRVVNexbu/camalmusalem · scanned 2026-06-16 01:07 UTC (2 months, 1 week ago)

69 raw signals (0 security + 69 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 68 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 12 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 68 Crowd 0 Layer: Frontend 7 Security 2 Cicd 2 Quality 26 Api 31

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 53.8/100 with 88.9% coverage. It contains 1741 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 69 findings — concentrated in api (31), quality (26), frontend (7). Risk profile is high: 0 critical, 5 high, 12 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 52 of 68 actionable findings. 69 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/settings.json

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

.claude/settings.json:82 SecretsClaude instruction

high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/upload-image (resources/js/lib/image-upload.ts:55)

`resources/js/lib/image-upload.ts:55` calls `POST /admin/upload-image` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/upload-image` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/upload-video (resources/js/lib/video-upload.ts:34)

`resources/js/lib/video-upload.ts:34` calls `POST /admin/upload-video` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/upload-video` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/vehicle-versions/${version!.id}/media (resources/js/pages/admin/vehicle-versions/form.tsx:304)

`resources/js/pages/admin/vehicle-versions/form.tsx:304` calls `POST /admin/vehicle-versions/${version!.id}/media` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/vehicle-versions/<p>/media` If this points at a…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /admin/vehicle-versions/bulk-import/preview (resources/js/pages/admin/vehicle-versions/bulk-import.tsx:82)

`resources/js/pages/admin/vehicle-versions/bulk-import.tsx:82` calls `POST /admin/vehicle-versions/bulk-import/preview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/admin/vehicle-versions/bulk-import/preview` If t…

Dangling fetchFetch

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — resources/js/pages/noticias/show.tsx:155

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — resources/js/hooks/use-two-factor-auth.ts:22

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — resources/js/lib/video-upload.ts:34

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/settings.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license, tests, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

medium System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in resources/js/pages/noticias/show.tsx:155

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

resources/js/pages/noticias/show.tsx:155 Dangerous innerhtml

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 301 placeholder/mock markers across 64 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 232 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality Docs conf 1.00 No README detected

No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.

ReadmeRepo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ownsOld` in resources/js/pages/admin/home/section-about.tsx:82

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/compliance/denuncias

`resources/js/pages/admin/compliance/index.tsx` declares `GET /admin/compliance/denuncias` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/cotizaciones-vehiculos

`resources/js/pages/admin/cotizaciones-vehiculos/index.tsx` declares `GET /admin/cotizaciones-vehiculos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or do…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/vehicle-versions

`resources/js/pages/admin/vehicle-versions/index.tsx` declares `GET /admin/vehicle-versions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /compliance/seguimiento

`resources/js/pages/compliance/seguimiento.tsx` declares `GET /compliance/seguimiento` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/accesorios

`resources/js/pages/admin/accesorios/form.tsx` declares `POST /admin/accesorios` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/branches

`resources/js/pages/admin/branches/form.tsx` declares `POST /admin/branches` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/brands

`resources/js/pages/admin/brands/form.tsx` declares `POST /admin/brands` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/cross-reference/import

`resources/js/components/admin/cross-reference-sync.tsx` declares `POST /admin/cross-reference/import` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/features

`resources/js/pages/admin/features/form.tsx` declares `POST /admin/features` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/formulario-mantencion/services

`resources/js/pages/admin/formulario-mantencion/index.tsx` declares `POST /admin/formulario-mantencion/services` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removi…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/formulario-mantencion/vehicle-models

`resources/js/pages/admin/formulario-mantencion/index.tsx` declares `POST /admin/formulario-mantencion/vehicle-models` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/features

`resources/js/pages/admin/home/section-features.tsx` declares `POST /admin/home/features` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who c…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/footer

`resources/js/pages/admin/home/section-footer.tsx` declares `POST /admin/home/footer` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/hero

`resources/js/pages/admin/home/section-hero.tsx` declares `POST /admin/home/hero` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/programas

`resources/js/pages/admin/home/section-programas.tsx` declares `POST /admin/home/programas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/seminuevos

`resources/js/pages/admin/home/section-seminuevos.tsx` declares `POST /admin/home/seminuevos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/home/shorts

`resources/js/pages/admin/home/section-shorts.tsx` declares `POST /admin/home/shorts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/logout

`resources/js/components/admin/admin-sidebar.tsx` declares `POST /admin/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/mantenimiento

`resources/js/pages/admin/maintenance/index.tsx` declares `POST /admin/mantenimiento` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/merch

`resources/js/pages/admin/merch/form.tsx` declares `POST /admin/merch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/noticias

`resources/js/pages/admin/noticias/form.tsx` declares `POST /admin/noticias` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/repuestos

`resources/js/pages/admin/repuestos/form.tsx` declares `POST /admin/repuestos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /admin/vehicle-versions/bulk-import

`resources/js/pages/admin/vehicle-versions/bulk-import.tsx` declares `POST /admin/vehicle-versions/bulk-import` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removin…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /cotizaciones/vehiculo

`resources/js/pages/nuevos/cotizar.tsx` declares `POST /cotizaciones/vehiculo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /kinto/solicitud

`resources/js/pages/kinto.tsx` declares `POST /kinto/solicitud` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /post-venta/agendar-mantencion

`resources/js/pages/post-venta/agendar-mantencion.tsx` declares `POST /post-venta/agendar-mantencion` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /post-venta/repuestos/encargo

`resources/js/pages/post-venta/repuestos.tsx` declares `POST /post-venta/repuestos/encargo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: resources/js/pages/admin/vehicle-models/form.tsx (1109 lines)