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.

Criptso/xcase-motion-website-v2

https://github.com/Criptso/xcase-motion-website-v2 · scanned 2026-06-17 01:24 UTC (1 month, 2 weeks ago)

7 raw signals (0 security + 7 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +14.7 (diff) · 7 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

44.4% cov · 7 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 6 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 7 Crowd 0 Layer: Frontend 1 Security 3 Quality 3

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 91.4/100 with 44.4% coverage. It contains 102 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in security (3), quality (3), frontend (1). Risk profile is low: 0 critical, 0 high, 6 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 7 of 7 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — assets/index--xxZNsph.js:9

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 — assets/index--xxZNsph.js:1

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 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 assets/index--xxZNsph.js:9

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

assets/index--xxZNsph.js:9 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in assets/index--xxZNsph.js:8

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

assets/index--xxZNsph.js:8 Direct innerhtml assignment

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `unstable_legacy` in assets/index--xxZNsph.js:8

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

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/06b6975b-6e95-4a81-8b7a-c5800546ab5d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/06b6975b-6e95-4a81-8b7a-c5800546ab5d/

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.