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.

xjanova/Thaiprompt-Affiliate

https://github.com/xjanova/Thaiprompt-Affiliate · scanned 2026-06-16 01:04 UTC (2 months, 1 week ago)

147 raw signals (0 security + 147 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 127 findings

Severity distribution — click a segment to filter

Active filters: layer: api × excluding tests × Reset all

Severity: Critical 5 High 14 Medium 33 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 127 Crowd 0 Layer: Frontend 45 Network 3 Hardware 1 Security 20 Cicd 4 Quality 29 Api 25

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 40.5/100 with 100.0% coverage. It contains 7079 nodes across 15 cross-layer flows, written primarily in mixed languages. Engine surfaced 147 findings — concentrated in frontend (45), quality (30), api (25). Risk profile is high: 5 critical, 14 high, 40 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 25 of 127 actionable findings. 147 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 api Wiring conf 1.00 Dangling fetch: GET /pos/api/customers/search?q=${query} (resources/js/pos/app.js:709)

`resources/js/pos/app.js:709` calls `GET /pos/api/customers/search?q=${query}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pos/api/customers/search` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /pos/api/products/all (public/pos-sw.js:658)

`public/pos-sw.js:658` calls `GET /pos/api/products/all` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pos/api/products/all` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /pos/api/products/search?q=${barcode} (resources/js/pos/app.js:359)

`resources/js/pos/app.js:359` calls `GET /pos/api/products/search?q=${barcode}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pos/api/products/search` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /taladsod/api/listings?${params} (resources/js/taladsod/app.js:103)

`resources/js/taladsod/app.js:103` calls `GET /taladsod/api/listings?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/taladsod/api/listings` If this points at an external API, prefix it with `https://` so t…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /user/crypto-wallet/prices (resources/js/crypto/charts.js:271)

`resources/js/crypto/charts.js:271` calls `GET /user/crypto-wallet/prices` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/user/crypto-wallet/prices` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/crypto/generate-nonce (resources/js/crypto/wallet-ui.js:257)

`resources/js/crypto/wallet-ui.js:257` calls `POST /api/crypto/generate-nonce` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crypto/generate-nonce` If this points at an external API, prefix it with `https://` so th…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/crypto/verify-signature (resources/js/crypto/wallet-ui.js:292)

`resources/js/crypto/wallet-ui.js:292` calls `POST /api/crypto/verify-signature` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/crypto/verify-signature` If this points at an external API, prefix it with `https://` s…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/api/display/cart/update (resources/js/pos/app.js:806)

`resources/js/pos/app.js:806` calls `POST /pos/api/display/cart/update` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pos/api/display/cart/update` If this points at an external API, prefix it with `https://` so the…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /pos/api/display/clear (resources/js/pos/app.js:832)

`resources/js/pos/app.js:832` calls `POST /pos/api/display/clear` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pos/api/display/clear` If this points at an external API, prefix it with `https://` so the matcher ski…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /qr-barcode/decode (public/js/qr-scanner.js:239)

`public/js/qr-scanner.js:239` calls `POST /qr-barcode/decode` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/qr-barcode/decode` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /cart/clear

`thaiprompt/services/api.ts` declares `DELETE /cart/clear` 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: GET /cart

`thaiprompt/services/api.ts` declares `GET /cart` 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: GET /orders

`thaiprompt/services/api.ts` declares `GET /orders` 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: GET /orders/unread-messages

`thaiprompt/services/api.ts` declares `GET /orders/unread-messages` 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: GET /payment/deposit-methods

`thaiprompt/services/api.ts` declares `GET /payment/deposit-methods` 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: GET /payment/history

`thaiprompt/services/api.ts` declares `GET /payment/history` 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: GET /payment/methods

`thaiprompt/services/api.ts` declares `GET /payment/methods` 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: GET /seller/orders

`thaiprompt/services/api.ts` declares `GET /seller/orders` 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: GET /seller/shipping-providers

`thaiprompt/services/api.ts` declares `GET /seller/shipping-providers` 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: GET /shipping-providers

`thaiprompt/services/api.ts` declares `GET /shipping-providers` 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 /cart/add

`thaiprompt/services/api.ts` declares `POST /cart/add` 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 /cart/checkout

`thaiprompt/services/api.ts` declares `POST /cart/checkout` 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 /cart/promo

`thaiprompt/services/api.ts` declares `POST /cart/promo` 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 /wallet/topup

`thaiprompt/services/api.ts` declares `POST /wallet/topup` 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 /web-session

`thaiprompt/services/api.ts` declares `POST /web-session` 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

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/a3139214-3e0d-488f-b938-7893036245d8/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a3139214-3e0d-488f-b938-7893036245d8/

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.