andyfangdz/approach-viz — Repobility public scan

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

andyfangdz/approach-viz

https://github.com/andyfangdz/approach-viz · scanned 2026-06-17 01:33 UTC (1 month, 2 weeks ago)

33 raw signals (0 security + 33 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

Security checks

88.9% cov · 26 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 14 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 26 Crowd 0 Layer: Frontend 3 Security 2 Cicd 2 Quality 19

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 77.1/100 with 88.9% coverage. It contains 917 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 33 findings — concentrated in quality (19), cicd (9), frontend (3). Risk profile is low: 0 critical, 0 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 26 actionable findings. 33 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.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/api/faa-plate/route.ts:26

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 — app/scene/chart/chart-tiles.worker.ts:56

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 — app/scene/nexrad/nexrad.worker.ts:132

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 — app/scene/SatelliteSurface.tsx:325

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 — app/scene/traffic/traffic.worker.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 — packages/approach-viz-core-wasm/approach_viz_core.js:843

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/approach_viz_core.js:843

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/service-worker.ts:111

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: AGENTS.md

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.

AGENTS.md VerificationAgents md

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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned

dtolnay/rust-toolchain@stable can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 2 locations

.github/workflows/macos-native.yml:37

.github/workflows/parser-tests.yml:50

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dev-with-ddtrace.mjs:3

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

scripts/dev-with-ddtrace.mjs:3 Node child process

medium System graph security Coverage conf 1.00 No auth library detected

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

auth

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

9 test file(s) for 152 source file(s) (ratio 0.06). Consider adding integration or unit tests for critical paths.

Coverage

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

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

CleanupRepo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 7 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

2 files, 7 locations

.github/workflows/parser-tests.yml:13, 16, 47, 53 (4 hits)

.github/workflows/macos-native.yml:15, 31, 42 (3 hits)

CI/CD securitySupply chainGithub actions

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/build-db.ts:386

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 quality Complexity conf 1.00 Very large file: services/runtime-rs/src/weather/phase_batch.rs (1236 lines)

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

low System graph quality Complexity conf 1.00 Very large file: services/runtime-rs/src/weather/processor.rs (1553 lines)

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

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/533dbaf0-43d4-4980-b2bb-4c9a0054ff3f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/533dbaf0-43d4-4980-b2bb-4c9a0054ff3f/

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.