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.

zealptl/lapwise

https://github.com/zealptl/lapwise · scanned 2026-06-16 01:11 UTC (2 months, 1 week ago)

54 raw signals (0 security + 54 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 45 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 13 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 45 Crowd 0 Layer: Software 2 Hardware 3 Security 2 Cicd 1 Quality 15 Api 22

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 64.4/100 with 100.0% coverage. It contains 1104 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 54 findings — concentrated in quality (24), api (22), hardware (3). Risk profile is low: 0 critical, 0 high, 13 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 40 of 45 actionable findings. 54 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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/apply.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.

.claude/commands/opsx/apply.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/opsx/archive.md

.claude/commands/opsx/archive.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json

.claude/settings.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. 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: service/Dockerfile

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

Container

medium System graph cicd CI/CD security conf 1.00 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.

.github/workflows/deploy-pages.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in lapwise-internal-demo.html:938

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

lapwise-internal-demo.html:938 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in infra/lib/lapwise-stack.ts:1

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

infra/lib/lapwise-stack.ts:1 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — agent/LapwiseF1Agent/app/LapwiseF1Agent/cognito.py:72

`urllib.request.urlopen(...)` 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 17 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: public.ecr.aws/lambda/python:3.12

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

service/Dockerfile:1 containersPinned dependencies

low System graph quality Integrity conf 1.00 10 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: service/src/lapwise/routes/v1/analysis/qualifying_trends.py:qualifying_trends, service/src/lapwise/routes/v1/analysis/driver_pace.py:driver_pace_profile This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/…

10 occurrences

repo-level (10 hits)

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 software Dead code conf 1.00 Possibly dead Python function: get_openf1_client

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

service/src/lapwise/deps.py:27

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

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

agent/LapwiseF1Agent/app/LapwiseF1Agent/main.py:104

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 api Wiring conf 1.00 Unused endpoint: GET /championship-context

`service/src/lapwise/routes/v1/analysis/championship_context.py` declares `GET /championship-context` 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 docum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /championship_drivers

`service/src/lapwise/routes/v1/championship_drivers.py` declares `GET /championship_drivers` 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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /championship_teams

`service/src/lapwise/routes/v1/championship_teams.py` declares `GET /championship_teams` 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 co…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /circuit-profile

`service/src/lapwise/routes/v1/analysis/circuit_profile.py` declares `GET /circuit-profile` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /constructor-pitstop

`service/src/lapwise/routes/v1/analysis/constructor_pitstop.py` declares `GET /constructor-pitstop` 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 documen…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /dnf-rates

`service/src/lapwise/routes/v1/analysis/dnf_rates.py` declares `GET /dnf-rates` 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 /driver-pace-profile

`service/src/lapwise/routes/v1/analysis/driver_pace.py` declares `GET /driver-pace-profile` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /drivers

`service/src/lapwise/routes/v1/drivers.py` declares `GET /drivers` 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 /fastest-lap-candidates

`service/src/lapwise/routes/v1/analysis/fastest_lap.py` declares `GET /fastest-lap-candidates` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /laps

`service/src/lapwise/routes/v1/laps.py` declares `GET /laps` 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 /meetings

`service/src/lapwise/routes/v1/meetings.py` declares `GET /meetings` 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 /overtake-profile

`service/src/lapwise/routes/v1/analysis/overtake_profile.py` declares `GET /overtake-profile` 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 w…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /overtakes

`service/src/lapwise/routes/v1/overtakes.py` declares `GET /overtakes` 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 /pit

`service/src/lapwise/routes/v1/pit.py` declares `GET /pit` 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 /position

`service/src/lapwise/routes/v1/position.py` declares `GET /position` 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 /prices

`service/src/lapwise/routes/v1/fantasy/prices.py` declares `GET /prices` 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 /qualifying-trends

`service/src/lapwise/routes/v1/analysis/qualifying_trends.py` declares `GET /qualifying-trends` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /session_result

`service/src/lapwise/routes/v1/session_result.py` declares `GET /session_result` 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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /sessions

`service/src/lapwise/routes/v1/sessions.py` declares `GET /sessions` 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 /starting_grid

`service/src/lapwise/routes/v1/starting_grid.py` declares `GET /starting_grid` 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 /stints

`service/src/lapwise/routes/v1/stints.py` declares `GET /stints` 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 /weather

`service/src/lapwise/routes/v1/weather.py` declares `GET /weather` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

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

For AI agents + API integrations

Email me when this repo regresses

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

API access

This page is publicly accessible at: https://repobility.com/scan/5246728f-96aa-4b65-9c85-094e961e4ba9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5246728f-96aa-4b65-9c85-094e961e4ba9/

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.