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.

adilch/WSCprep

https://github.com/adilch/WSCprep · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

36 raw signals (0 security + 36 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 36 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 13 Medium 10 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 36 Crowd 0 Layer: Software 1 Frontend 4 Hardware 2 Security 2 Quality 14 Api 13

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 65.0/100 with 77.8% coverage. It contains 270 nodes across 9 cross-layer flows, written primarily in mixed languages. Engine surfaced 36 findings — concentrated in quality (14), api (13), frontend (4). Risk profile is high: 0 critical, 13 high, 10 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 29 of 36 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 1.00 Dangling fetch: GET /api/stations (web/components/FrequencyView.tsx:254)

`web/components/FrequencyView.tsx:254` calls `GET /api/stations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations` 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 /api/stations/${id}/daily?variable=discharge (web/components/CompareView.tsx:73)

`web/components/CompareView.tsx:73` calls `GET /api/stations/${id}/daily?variable=discharge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//daily` If this points at an external API, prefix it with `http…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${id}/peaks (web/components/CompareView.tsx:75)

`web/components/CompareView.tsx:75` calls `GET /api/stations/${id}/peaks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//peaks` If this points at an external API, prefix it with `https://` so the matche…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${stationId} (web/components/FrequencyView.tsx:252)

`web/components/FrequencyView.tsx:252` calls `GET /api/stations/${stationId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations/` If this points at an external API, prefix it with `https://` so the matcher …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${stationId}/daily?variable=${v} (web/components/HistoricDataView.tsx:87)

`web/components/HistoricDataView.tsx:87` calls `GET /api/stations/${stationId}/daily?variable=${v}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//daily` If this points at an external API, prefix it wit…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${stationId}/daily?variable=discharge (web/components/FrequencyView.tsx:239)

`web/components/FrequencyView.tsx:239` calls `GET /api/stations/${stationId}/daily?variable=discharge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//daily` If this points at an external API, prefix it …

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${stationId}/daily?variable=discharge (web/components/ReportView.tsx:142)

`web/components/ReportView.tsx:142` calls `GET /api/stations/${stationId}/daily?variable=discharge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//daily` If this points at an external API, prefix it wit…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/stations/${stationId}/peaks (web/components/FrequencyView.tsx:223)

`web/components/FrequencyView.tsx:223` calls `GET /api/stations/${stationId}/peaks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//peaks` 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 /api/stations/${stationId}/peaks (web/components/ReportView.tsx:144)

`web/components/ReportView.tsx:144` calls `GET /api/stations/${stationId}/peaks` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//peaks` 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 /api/stations/${s.id}/frequency (web/components/CompareView.tsx:160)

`web/components/CompareView.tsx:160` calls `POST /api/stations/${s.id}/frequency` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//frequency` 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 /api/stations/${stationId}/frequency (web/components/FrequencyView.tsx:498)

`web/components/FrequencyView.tsx:498` calls `POST /api/stations/${stationId}/frequency` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//frequency` If this points at an external API, prefix it with `http…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /api/stations/${stationId}/frequency (web/components/ReportView.tsx:146)

`web/components/ReportView.tsx:146` calls `POST /api/stations/${stationId}/frequency` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/stations//frequency` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph security auth conf 1.00 FastAPI POST `flood_frequency` without auth dependency — ffa-service/app/main.py:32

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

ffa-service/app/main.py:32 securityAuth fastapi unauth mutation

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — web/components/CompareView.tsx:73

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 — web/components/FrequencyView.tsx:498

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 — web/components/ReportView.tsx:142

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 — web/lib/ogc.ts:14

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/launch.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/launch.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 ci, tests. 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 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 hardware Security conf 1.00 Dockerfile runs as root: ffa-service/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

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

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

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

Coverage

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

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

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 7 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

ffa-service/Dockerfile:1 containersPinned dependencies

low System graph software Dead code conf 1.00 Possibly dead Python function: feature_card

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

make_presentation.py:96

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/flood-frequency

`ffa-service/app/main.py` declares `POST /api/v1/flood-frequency` 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 quality Complexity conf 1.00 Very large file: web/components/FrequencyView.tsx (2068 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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/c7d5fa36-2d2c-4e12-9218-af835b16b0c9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c7d5fa36-2d2c-4e12-9218-af835b16b0c9/

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.