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.

pregasquad/PREGA

https://github.com/pregasquad/PREGA · scanned 2026-09-01 12:04 UTC (1 month, 3 weeks ago)

280 raw signals (0 security + 280 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 280 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 · 280 findings

Severity distribution — click a segment to filter

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

Severity: Critical 3 High 110 Medium 93 Low 53 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 280 Crowd 0 Layer: Frontend 30 Security 184 Hardware 2 Cicd 1 Quality 29 Dependencies 26 Api 8

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 76.8/100 with 100.0% coverage. It contains 2239 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 280 findings — concentrated in security (184), frontend (30), quality (29). Risk profile is high: 3 critical, 110 high, 93 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 8 of 280 actionable findings. 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 0.90 Dangling fetch: DELETE /api/appointments/${id} (artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:131)

`artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:131` calls `DELETE /api/appointments/${id}` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matchi…

artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:131 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: GET /api/export/${type} (artifacts/pregasquad-manager/src/pages/AdminSettings.tsx:531)

`artifacts/pregasquad-manager/src/pages/AdminSettings.tsx:531` calls `GET /api/export/${type}` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matching: `/ex…

artifacts/pregasquad-manager/src/pages/AdminSettings.tsx:531 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: GET /api/notifications/broadcast/last (artifacts/pregasquad-manager/src/pages/WhatsApp.tsx:1025)

`artifacts/pregasquad-manager/src/pages/WhatsApp.tsx:1025` calls `GET /api/notifications/broadcast/last` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matc…

artifacts/pregasquad-manager/src/pages/WhatsApp.tsx:1025 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: POST /api/appointments (artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:108)

`artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:108` calls `POST /api/appointments` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matching: `/ap…

artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:108 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: POST /api/appointments (artifacts/pregasquad-manager/src/pages/Clients.tsx:264)

`artifacts/pregasquad-manager/src/pages/Clients.tsx:264` calls `POST /api/appointments` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matching: `/appointme…

artifacts/pregasquad-manager/src/pages/Clients.tsx:264 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: POST /api/appointments (artifacts/pregasquad-manager/src/pages/POS.tsx:195)

`artifacts/pregasquad-manager/src/pages/POS.tsx:195` calls `POST /api/appointments` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matching: `/appointments`

artifacts/pregasquad-manager/src/pages/POS.tsx:195 Dangling fetchFetch

high System graph api Wiring conf 0.90 Dangling fetch: PUT /api/appointments/${id} (artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:92)

`artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:92` calls `PUT /api/appointments/${id}` but no backend route in the scanned graph matches that path. This is a likely runtime 404 unless an external gateway or unsupported router provides it. Tool: fetch Normalized path used for matching: …

artifacts/pregasquad-manager/src/pages/BookingHistory.tsx:92 Dangling fetchFetch

low System graph api Wiring conf 1.00 146 backend endpoints not called by scanned frontend

No scanned frontend call matched these backend routes. Sample: USE /uploads, GET /logs/stream, GET /api/logs, GET /api/logs/stream, GET /api/public/page-views, POST /api/public/page-views, GET /api/public/website-testimonials, GET /api/website-testimonials + 138 more. This is fine when endpoints se…

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/27185afd-42ec-4e25-9404-3a8383de3555/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/27185afd-42ec-4e25-9404-3a8383de3555/

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.