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.
Sign up free Scan another repo

shanestratton/thalassa-marine-weather

https://github.com/shanestratton/thalassa-marine-weather · scanned 2026-06-16 00:09 UTC (2 months, 2 weeks ago)

756 raw signals (12 security + 744 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 708 actionable findings from 2 signal sources. 63 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
34.1
/100
Security checks
34
6 findings
System graph
34
100.0% cov · 702 findings
Critical
7
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 7 High 19 Medium 160 Low 180 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 6 System graph 702 Crowd 0 Layer: Quality 428 Security 57 Software 4 Frontend 141 Network 3 Hardware 5 Cicd 4 Api 66
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 34.1/100 with 100.0% coverage. It contains 7136 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 744 findings — concentrated in quality (425), frontend (141), api (66). Risk profile is high: 6 critical, 17 high, 166 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 366 of 708 actionable findings. 771 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.

critical Security checks security auth conf 0.78 Foundry mined security auth guardrail gaps: shanestratton/thalassa-marine-weather
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in supabase/functions/fetch-weatherkit/index.ts:56
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
supabase/functions/fetch-weatherkit/index.ts:56 Private key in repo
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in supabase/functions/get-weather/index.ts:158
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
supabase/functions/get-weather/index.ts:158 Private key in repo
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in supabase/functions/send-anchor-alarm/index.ts:30
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
supabase/functions/send-anchor-alarm/index.ts:30 Private key in repo
critical System graph security security conf 1.00 Insecure pattern 'private_key_in_repo' in supabase/functions/send-push/index.ts:64
Found a known-risky pattern (private_key_in_repo). Review and replace if possible.
supabase/functions/send-push/index.ts:64 Private key in repo
critical System graph security Secrets conf 1.00 Possible secret in bosun-pi/bosun_network_apply.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
bosun-pi/bosun_network_apply.py:46
critical System graph security Secrets conf 1.00 Possible secret in pi-cache/setup-opencpn.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
pi-cache/setup-opencpn.sh:94
high Security checks quality Practices conf 0.84 5 occurrences Foundry mined bad chains: shanestratton/thalassa-marine-weather
Comment chain pattern product: bad_chains Repo: shanestratton/thalassa-marine-weather Thread: shanestratton/thalassa-marine-weather#7 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph…
5 occurrences
repo-level (5 hits)
high Security checks quality Testing conf 0.78 6 occurrences Foundry mined test ci gap after feedback: shanestratton/thalassa-marine-weather
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
6 occurrences
repo-level (6 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /pcm-worklet.js (services/voice/deepgramRecognizer.ts:543)
`services/voice/deepgramRecognizer.ts:543` calls `GET /pcm-worklet.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/pcm-worklet.js` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /wind_test.json (components/map/MapboxVelocityOverlay.tsx:430)
`components/map/MapboxVelocityOverlay.tsx:430` calls `GET /wind_test.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/wind_test.json` 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: GET https://api.stormglass.io/... (utils/rateLimiter.ts:13)
`utils/rateLimiter.ts:13` calls `GET https://api.stormglass.io/...` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.stormglass.io/...` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://customer-api.open-meteo.com/v1/forecast?${params} (services/weather/pointWeather.ts:94)
`services/weather/pointWeather.ts:94` calls `GET https://customer-api.open-meteo.com/v1/forecast?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/customer-api.open-meteo.com/v1/forecast` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://customer-api.open-meteo.com/v1/marine?${params} (services/weather/pointWeather.ts:131)
`services/weather/pointWeather.ts:131` calls `GET https://customer-api.open-meteo.com/v1/marine?${params}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/customer-api.open-meteo.com/v1/marine` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://gmail.googleapis.com/gmail/v1${path} (services/voice/integrations/gmail.ts:413)
`services/voice/integrations/gmail.ts:413` calls `GET https://gmail.googleapis.com/gmail/v1${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/gmail.googleapis.com/gmail/v1/<p>` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://nominatim.openstreetmap.org/reverse?lat=${loc.lat}&lon=${loc.lon}&format=json&zoom=10&addressdetails=1 (hooks/useCrewFinderActions.ts:276)
`hooks/useCrewFinderActions.ts:276` calls `GET https://nominatim.openstreetmap.org/reverse?lat=${loc.lat}&lon=${loc.lon}&format=json&zoom=10&addressdetails=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/no…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.googleapis.com/oauth2/v2/userinfo (services/voice/integrations/gmail.ts:324)
`services/voice/integrations/gmail.ts:324` calls `GET https://www.googleapis.com/oauth2/v2/userinfo` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.googleapis.com/oauth2/v2/userinfo` If this points at an …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.anthropic.com/v1/messages (supabase/functions/proxy-bosun-fallback/index.ts:194)
`supabase/functions/proxy-bosun-fallback/index.ts:194` calls `POST https://api.anthropic.com/v1/messages` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.anthropic.com/v1/messages` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/speech-to-text (supabase/functions/proxy-bosun-fallback/index.ts:562)
`supabase/functions/proxy-bosun-fallback/index.ts:562` calls `POST https://api.elevenlabs.io/v1/speech-to-text` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/speech-to-text` If this poin…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId} (supabase/functions/elevenlabs-tts/index.ts:239)
`supabase/functions/elevenlabs-tts/index.ts:239` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-speech/<p>` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId} (supabase/functions/proxy-bosun-fallback/index.ts:494)
`supabase/functions/proxy-bosun-fallback/index.ts:494` calls `POST https://api.elevenlabs.io/v1/text-to-speech/${voiceId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.elevenlabs.io/v1/text-to-speech/<p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://nominatim.openstreetmap.org/reverse?lat=${lat}&lon=${lon}&format=json&zoom=14&addressdetails=1 (services/DiaryService.ts:982)
`services/DiaryService.ts:982` calls `POST https://nominatim.openstreetmap.org/reverse?lat=${lat}&lon=${lon}&format=json&zoom=14&addressdetails=1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/nominatim.open…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (services/voice/integrations/gmail.ts:165)
`services/voice/integrations/gmail.ts:165` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://oauth2.googleapis.com/token (services/voice/integrations/gmail.ts:296)
`services/voice/integrations/gmail.ts:296` calls `POST https://oauth2.googleapis.com/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/oauth2.googleapis.com/token` If this points at an external API, prefi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://overpass-api.de/api/interpreter (supabase/functions/route-weather/index.ts:222)
`supabase/functions/route-weather/index.ts:222` calls `POST https://overpass-api.de/api/interpreter` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/overpass-api.de/api/interpreter` If this points at an extern…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in services/AvNavDiscoveryService.ts:110
Found a known-risky pattern (new_function_used). Review and replace if possible.
services/AvNavDiscoveryService.ts:110 New function used
medium Security checks quality Practices conf 0.62 Foundry mined assumption checks: shanestratton/thalassa-marine-weather
Comment chain pattern product: assumption_checks Repo: shanestratton/thalassa-marine-weather Thread: shanestratton/thalassa-marine-weather#6 Outcome: claimed_resolved_unverified Thread label: thread_has_human_issue_and_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source…
medium Security checks quality maintenance conf 0.70 7 occurrences Foundry mined blueprint gap alignment: shanestratton/thalassa-marine-weather
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
7 occurrences
repo-level (7 hits)
medium Security checks quality Practices conf 0.70 7 occurrences Foundry mined unresolved feedback: shanestratton/thalassa-marine-weather
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: supp…
7 occurrences
repo-level (7 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — api/chl/[file].ts:25
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 — api/currents/[file].ts:39
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 — api/mld/[file].ts:25
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 — api/mpa/[file].ts:30
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 — api/seaice/[file].ts:25
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 — api/sst/[file].ts:28
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 — api/waves/[file].ts:38
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 — cloudflare-worker/src/index.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 — components/diary/SwipeableDiaryCard.tsx:81
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 — components/map/MapboxVelocityOverlay.tsx:430
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 — components/map/useMapInit.ts:759
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 — components/map/usePassagePlanner.ts:1358
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 — components/map/useWeatherLayers.ts:1444
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 — components/marketplace/CreateListingModal.tsx:146
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 — components/passage/PassageCanvas.tsx:395
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 — components/vessel/DocumentsHub.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 — hooks/chat/useChatProposals.ts:74
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 — hooks/useVoyageForm.ts:873
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 — middleware.ts:47
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 — pi-cache/src/routes/charts.ts:231
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 — pi-cache/src/server.ts:13
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 — pi-cache/src/services/osm.ts:192
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 — public/sw.js:115
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 — scripts/audit-reef-edge-markers.mjs:110
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 — services/AisStreamService.ts:76
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 — services/AvNavService.ts:1378
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 — services/ChartLockerService.ts:1149
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 — services/ConnectionPriorityService.ts:141
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 — services/ConsensusMatrixEngine.ts:115
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 — services/DiaryService.ts:1025
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 — services/GalleyRecipeService.ts:487
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 — services/geminiService.ts:57
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 — services/InshoreRouter.ts:1970
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 — services/MapboxDirectionsService.ts:92
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 — services/MBTilesService.ts:103
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 — services/native/weatherKit.ts:29
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 — services/NoticeToMarinersService.ts:318
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 — services/PiCacheService.ts:906
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 — services/SatLinkClient.ts:157
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 — services/voice/bosunVoice.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — services/voice/cloudFallback.ts:15
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 — services/voice/cloudTools.ts:53
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 — services/voice/integrations/gmail.ts:324
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 — services/weather/api/chlGrid.ts:59
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 — services/weather/api/currentsGrid.ts:59
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 — services/weather/api/globalWind.ts:106
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 — services/weather/api/mldGrid.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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — services/weather/api/rainbowPrecip.ts:148
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 — services/weather/api/rainviewerIndex.ts:18
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 — services/weather/api/seaiceGrid.ts:38
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 — services/weather/api/sstGrid.ts:59
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 — services/weather/api/stormglass.ts:149
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 — services/weather/api/wavesGrid.ts:59
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 — services/weather/api/worldtides.ts:13
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 — services/weather/CycloneTrackingService.ts:175
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 — services/weather/isobars.ts:269
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 — services/weather/pointWeather.ts:94
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 — services/weather/ResumableGribFetcher.ts:50
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 — services/weather/useGribDownload.ts:4
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 — services/weather/windField.ts:270
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 — services/WeatherWindowService.ts:250
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 — services/ww3CacheClient.ts:136
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 — supabase/functions/check-weather-alerts/index.ts:149
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 — supabase/functions/elevenlabs-tts/index.ts:239
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 — supabase/functions/fetch-wind-velocity/index.ts:416
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 — supabase/functions/get-weather/index.ts:247
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 — supabase/functions/proxy-amsa-msi/index.ts:155
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 — supabase/functions/proxy-bosun-fallback/index.ts:194
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 — supabase/functions/proxy-gemini/index.ts:85
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 — supabase/functions/proxy-linz-msi/index.ts:11
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 — supabase/functions/proxy-openmeteo/index.ts:68
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 — supabase/functions/proxy-overpass/index.ts:133
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 — supabase/functions/proxy-rainbow/index.ts:84
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 — supabase/functions/proxy-stormglass/index.ts:76
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 — supabase/functions/proxy-tides/index.ts:88
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 — supabase/functions/proxy-ukho-msi/index.ts:104
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 — supabase/functions/route-bathymetric/index.ts:210
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 — supabase/functions/route-weather/index.ts:1303
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 — supabase/functions/satellite-tile/index.ts:88
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 — supabase/functions/scrape-vessel-metadata/_shared/scrapers/AmsaScraper.ts:40
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 — supabase/functions/scrape-vessel-metadata/_shared/scrapers/EquasisScraper.ts:89
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 — supabase/functions/send-push/index.ts:202
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 — sw.js:103
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 — utils/gpsFollow.ts:47
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 — utils/logExportHelpers.ts:75
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 — utils/pdfExport.ts:419
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 — utils/rateLimiter.ts:13
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 — vessel-scraper/src/scrapers/AmsaScraper.ts:50
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 — vessel-scraper/src/scrapers/EquasisScraper.ts:105
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 license, lockfile. 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: vessel-scraper/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: workers/ais-ingest/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
github/codeql-action/init@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/codeql.yml:32, 39, 42 (3 hits)
.github/workflows/lighthouse.yml:37
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
7 files, 7 locations
.github/workflows/cmems-chl-pipeline.yml
.github/workflows/cmems-currents-pipeline.yml
.github/workflows/cmems-mld-pipeline.yml
.github/workflows/cmems-seaice-pipeline.yml
.github/workflows/cmems-sst-pipeline.yml
.github/workflows/cmems-waves-pipeline.yml
.github/workflows/mpa-pipeline.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in pi-cache/src/server.ts:48
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
pi-cache/src/server.ts:48 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in public/voyage-log-api.html:167
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
public/voyage-log-api.html:167 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in scripts/mock-signalk-server.cjs:110
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
scripts/mock-signalk-server.cjs:110 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/anthropic-proxy/index.ts:30
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/anthropic-proxy/index.ts:30 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/capture-escrow-payment/index.ts:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/capture-escrow-payment/index.ts:16 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/create-marketplace-payment/index.ts:20
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/create-marketplace-payment/index.ts:20 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/deepgram-token/index.ts:41
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/deepgram-token/index.ts:41 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/elevenlabs-tts/index.ts:34
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/elevenlabs-tts/index.ts:34 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-gfs-tracker/index.ts:19
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-gfs-tracker/index.ts:19 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-precip-grid/index.ts:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-precip-grid/index.ts:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-pressure-grid/index.ts:16
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-pressure-grid/index.ts:16 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-weatherkit/index.ts:30
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-weatherkit/index.ts:30 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-wind-grid/index.ts:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-wind-grid/index.ts:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/fetch-wind-velocity/index.ts:24
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/fetch-wind-velocity/index.ts:24 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/gebco-depth/index.ts:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/gebco-depth/index.ts:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/gemini-diary/index.ts:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/gemini-diary/index.ts:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/get-weather/index.ts:34
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/get-weather/index.ts:34 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/lookup-user/index.ts:19
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/lookup-user/index.ts:19 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/lookup-vessel/index.ts:22
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/lookup-vessel/index.ts:22 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/maritime-intel/index.ts:11
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/maritime-intel/index.ts:11 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/musickit-token/index.ts:42
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/musickit-token/index.ts:42 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-amsa-msi/index.ts:38
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-amsa-msi/index.ts:38 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-bosun-fallback/index.ts:30
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-bosun-fallback/index.ts:30 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-gemini/index.ts:29
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-gemini/index.ts:29 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-himawari-ir/index.ts:22
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-himawari-ir/index.ts:22 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-linz-msi/index.ts:37
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-linz-msi/index.ts:37 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-openmeteo/index.ts:22
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-openmeteo/index.ts:22 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-overpass/index.ts:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-overpass/index.ts:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-rainbow/index.ts:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-rainbow/index.ts:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-stormglass/index.ts:23
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-stormglass/index.ts:23 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-tides/index.ts:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-tides/index.ts:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/proxy-ukho-msi/index.ts:27
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/proxy-ukho-msi/index.ts:27 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/route-bathymetric/index.ts:25
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/route-bathymetric/index.ts:25 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/route-weather/index.ts:32
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/route-weather/index.ts:32 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/satellite-tile/index.ts:26
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/satellite-tile/index.ts:26 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/scrape-vessel-metadata/index.ts:32
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/scrape-vessel-metadata/index.ts:32 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/sweep-expired-escrows/index.ts:15
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/sweep-expired-escrows/index.ts:15 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/sweep-stale-vessels/index.ts:10
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/sweep-stale-vessels/index.ts:10 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/vessels-nearby/index.ts:18
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/vessels-nearby/index.ts:18 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/voyage-log/index.ts:40
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/voyage-log/index.ts:40 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in vite.config.ts:202
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
vite.config.ts:202 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in components/map/useAisStreamLayer.ts:764
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
components/map/useAisStreamLayer.ts:764 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in components/map/useCycloneLayer.ts:2003
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
components/map/useCycloneLayer.ts:2003 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in components/map/useDestinationFlag.ts:87
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
components/map/useDestinationFlag.ts:87 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in components/map/useVesselTracker.ts:74
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
components/map/useVesselTracker.ts:74 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in components/ChatPage.tsx:754
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
components/ChatPage.tsx:754 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in pi-cache/src/encWatcher.ts:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
pi-cache/src/encWatcher.ts:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in pi-cache/src/routes/enc.ts:51
Found a known-risky pattern (node_child_process). Review and replace if possible.
pi-cache/src/routes/enc.ts:51 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tools/senc-extractor/src/oexserverd.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
tools/senc-extractor/src/oexserverd.ts:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-chl-pipeline/pipeline.py:219
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-currents-pipeline/pipeline.py:209
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-mld-pipeline/pipeline.py:223
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-seaice-pipeline/pipeline.py:219
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-sst-pipeline/pipeline.py:208
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/cmems-waves-pipeline/pipeline.py:235
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/mpa-pipeline/pipeline.py:256
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 418 placeholder/mock markers across 121 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 network Security conf 1.00 Privileged port 14 in use
Port 14 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/cmems-sst-pipeline.yml Ports
medium System graph network Security conf 1.00 Privileged port 15 in use
Port 15 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/cmems-sst-pipeline.yml Ports
medium System graph network Security conf 1.00 Privileged port 17 in use
Port 17 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/mpa-pipeline.yml Ports
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — components/SettingsModal.tsx:56
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — components/SystemStatusButton.tsx:456
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph quality Integrity conf 1.00 61 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AISSTREAM_KEY`, `AMSA_API_URL`, `API_KEY`, `BATCH_FLUSH_MS`, `BATCH_MAX_SIZE`, `BOSUN_USER_ID`, `BOUNDING_BOXES`, `CHART_DIR` + 53 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, lockfile. 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 hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 953 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: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
vessel-scraper/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
workers/ais-ingest/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 32 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
12 files, 32 locations
.github/workflows/ci.yml:25, 78, 88 (3 hits)
.github/workflows/cmems-chl-pipeline.yml:18, 21, 41 (3 hits)
.github/workflows/cmems-currents-pipeline.yml:21, 24, 44 (3 hits)
.github/workflows/cmems-mld-pipeline.yml:18, 21, 41 (3 hits)
.github/workflows/cmems-seaice-pipeline.yml:18, 21, 41 (3 hits)
.github/workflows/cmems-sst-pipeline.yml:20, 23, 43 (3 hits)
.github/workflows/cmems-waves-pipeline.yml:21, 24, 44 (3 hits)
.github/workflows/linz-msi-scrape.yml:32, 35, 60 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — components/map/useAisStreamLayer.ts:766
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — stories/AuthBanner.stories.tsx:27
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — stories/ToastNotification.stories.tsx:35
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Tests conf 1.00 Low test-to-source ratio
243 tests / 987 src (ratio 0.25).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/build_nav_graph.py:node, scripts/build_nav_graph.py:node This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: scripts/build_nav_graph.py:way, scripts/build_nav_graph.py:way, scripts/build_nav_graph.py:way This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're sepa…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: scripts/cmems-sst-pipeline/pipeline.py:require_env, scripts/cmems-chl-pipeline/pipeline.py:require_env, scripts/mpa-pipeline/pipeline.py:require_env, scripts/cmems-seaice-pipeline/pipeline.py:require_env This is *the* AI-coder failure mode (4× more d…
duplicatesduplication
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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: scripts/linz-msi-scrape/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
scripts/linz-msi-scrape/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: tools/senc-extractor/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
tools/senc-extractor/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: vessel-scraper/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
vessel-scraper/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `Active_Hurricanes_v1` in services/weather/CycloneTrackingService.ts:54
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 Integrity conf 1.00 Old/deprecated-named symbol `cloud_old` in tests/voyageData.test.ts:329
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 Integrity conf 1.00 Old/deprecated-named symbol `daysOld` in components/vessel/EncCellManager.tsx:77
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 Integrity conf 1.00 Old/deprecated-named symbol `scribe_v1` in supabase/functions/proxy-bosun-fallback/index.ts:550
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 Integrity conf 1.00 Old/deprecated-named symbol `seamark_cache_v2` in services/SeamarkService.ts:57
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_anchor_view_coach_v1` in components/dashboard/hero/EssentialAnchorView.tsx:354
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_chat_channels_v1` in services/chat/constants.ts:16
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_chat_channels_v1` in tests/ChatService.test.ts:294
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_diary_entries_v2` in services/DiaryService.ts:76
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_hero_pin_coach_v1` in components/dashboard/HeroHeader.tsx:252
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_hero_pin_coach_v1` in components/ui/CoachMark.tsx:15
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_map_enc_chart_detail_v2` in components/map/MapHub.tsx:401
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_mob_active_v1` in services/MobService.ts:19
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_ntm_cache_v1` in services/NoticeToMarinersService.ts:279
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_smart_polars_v1` in services/SmartPolarStore.ts:9
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_swipe_hint_seen_v1` in components/dashboard/HeroSlide.tsx:268
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_tooltip_tour_v2` in components/ui/OnboardingTooltips.tsx:16
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_voyage_cache_v2` in services/nativeStorage.ts: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
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `thalassa_voyage_track_cache_v1` in services/shiplog/VoyageTrackCache.ts:28
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 Integrity conf 1.00 Old/deprecated-named symbol `thalassa_wt_rate_v1` in services/weather/api/worldtides.ts:24
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: decode_type
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
vessel-scraper/extract_marine_cadastre.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: relation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scan_depth_fairway.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: way
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scan_depth_fairway.py:25
low System graph software Dead code conf 1.00 Possibly dead Python function: way
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_nav_graph.py:556
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cloudflare-worker/src/index.ts:185
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — pi-cache/src/encWatcher.ts:63
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — pi-cache/src/routes/charts.ts:381
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — pi-cache/src/scheduler.ts:78
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — pi-cache/src/server.ts:132
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/build_channel_walls.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-bundle-size.js:52
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-apple-client-secret.js:80
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/voice/deepgramRecognizer.ts:168
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — services/voice/speechRecognizer.ts:80
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/anthropic-proxy/index.ts:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/check-weather-alerts/index.ts:362
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/deepgram-token/index.ts:133
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/deepgram-ws-proxy/index.ts:69
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/lookup-vessel/index.ts:287
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/maritime-intel/index.ts:115
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/proxy-bosun-fallback/index.ts:257
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/scrapers/AisSeedScraper.ts:315
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/scrapers/AmsaScraper.ts:29
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/scrapers/EquasisScraper.ts:30
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/scrapers/ItuMarsScraper.ts:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/scrapers/UscgScraper.ts:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/_shared/supabase.ts:124
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/scrape-vessel-metadata/index.ts:49
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/send-push/index.ts:325
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — supabase/functions/sweep-stale-vessels/index.ts:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/senc-extractor/src/cli.ts:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/senc-extractor/src/decryptBatch.ts:136
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/senc-extractor/src/extract.ts:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/senc-extractor/src/routeTest.ts:110
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — tools/senc-extractor/src/scan.ts:146
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/import-csv.ts:240
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/index.ts:38
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/scrapers/AisSeedScraper.ts:331
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/scrapers/AmsaScraper.ts:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/scrapers/EquasisScraper.ts:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/scrapers/ItuMarsScraper.ts:26
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/scrapers/UscgScraper.ts:34
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — vessel-scraper/src/supabase.ts:143
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — workers/ais-ingest/db.ts:35
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — workers/ais-ingest/index.ts:67
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — workers/ais-ingest/watchdog.ts:40
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /configure
`bosun-pi/bosun_network_api.py` declares `ANY /configure` 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: ANY /scan
`bosun-pi/bosun_network_api.py` declares `ANY /scan` 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: DELETE /local/:name
`pi-cache/src/routes/charts.ts` declares `DELETE /local/:name` 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 /api/passthrough
`pi-cache/src/server.ts` declares `GET /api/passthrough` 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 /api/passthrough-tile
`pi-cache/src/server.ts` declares `GET /api/passthrough-tile` 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 /buoys
`pi-cache/src/routes/misc.ts` declares `GET /buoys` 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 /buoys/:stationId
`pi-cache/src/routes/misc.ts` declares `GET /buoys/:stationId` 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 /combined
`pi-cache/src/routes/weather.ts` declares `GET /combined` 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 /composite
`pi-cache/src/routes/grib.ts` declares `GET /composite` 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 /current
`pi-cache/src/routes/weather.ts` declares `GET /current` 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 /cyclones
`pi-cache/src/routes/misc.ts` declares `GET /cyclones` 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 /cyclones/:id
`pi-cache/src/routes/misc.ts` declares `GET /cyclones/:id` 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 /forecast
`pi-cache/src/routes/weather.ts` declares `GET /forecast` 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 /gebco/:z/:x/:y
`pi-cache/src/routes/tiles.ts` declares `GET /gebco/:z/:x/:y` 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 /geocode
`pi-cache/src/routes/misc.ts` declares `GET /geocode` 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 /gibs/:layer/:z/:x/:y
`pi-cache/src/routes/tiles.ts` declares `GET /gibs/:layer/:z/:x/:y` 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 /jobs
`pi-cache/src/routes/charts.ts` declares `GET /jobs` 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 /jobs/:id
`pi-cache/src/routes/charts.ts` declares `GET /jobs/:id` 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 /local
`pi-cache/src/routes/charts.ts` declares `GET /local` 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 /marine
`pi-cache/src/routes/weather.ts` declares `GET /marine` 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 /noaa
`pi-cache/src/routes/grib.ts` declares `GET /noaa` 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 /nowcoast/:layer/:z/:x/:y
`pi-cache/src/routes/tiles.ts` declares `GET /nowcoast/:layer/:z/:x/:y` 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 /openseamap/:z/:x/:y
`pi-cache/src/routes/tiles.ts` declares `GET /openseamap/:z/:x/:y` 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 /overlay
`pi-cache/src/routes/osm.ts` declares `GET /overlay` 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 /precip
`pi-cache/src/routes/grib.ts` declares `GET /precip` 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 /precipitation
`pi-cache/src/routes/misc.ts` declares `GET /precipitation` 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

Showing first 300 of 366. Refine filters or use the findings page for deep search.

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/2eefa879-6c0c-490e-ba9c-2a3dbe6ae97d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2eefa879-6c0c-490e-ba9c-2a3dbe6ae97d/

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.