latchbio/latch

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.

76 of your 171 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.78s · analysis 6.94s · 2.8 MB · GitHub preflight 434ms

https://github.com/latchbio/latch · scanned 2026-06-05 19:37 UTC (4 days, 16 hours ago) · 10 languages

338 raw signals (156 security + 182 graph) 39th percentile · Python · medium (20-100K LoC) System graph score 70 (lower by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 179 actionable findings from 2 signal sources. 66 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 · 80 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	17.6	0.25	4.40
`testing_score`	12.0	0.20	2.40
`documentation_score`	86.0	0.15	12.90
`practices_score`	74.0	0.15	11.10
`code_quality`	52.9	0.10	5.29
Overall		1.00	48.8

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 56 Medium 32 Low 62 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 99 System graph 80 Crowd 0 Layer: Security 12 Software 73 Cicd 11 Quality 75 Api 1 Hardware 6 Frontend 1

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

.env file present in repo: src/latch_cli/services/init/assemble_and_sort/.env

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.

Insecure pattern 'exec_used' in src/latch_cli/services/launch/launch.py:49

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/latch_cli/services/launch/launch.py:49

Dockerfile pipes a remote installer into a shell

GapSeverity.HIGH Layer.HARDWARE score 0.375

Why: high severity

src/latch_cli/services/init/example_nfcore/Dockerfile:10

Insecure pattern 'subprocess_shell_true' in src/latch_cli/services/init/init.py:106

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/latch_cli/services/init/init.py:106

Insecure pattern 'subprocess_shell_true' in src/latch_cli/services/init/assemble_and_sort/assemble.py:36

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/latch_cli/services/init/assemble_and_sort/assemble.py:36

Insecure pattern 'subprocess_shell_true' in src/latch_cli/services/init/assemble_and_sort/sort.py:29

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

src/latch_cli/services/init/assemble_and_sort/sort.py:29

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/test.yaml:16

Dockerfile runs as root: src/latch_cli/services/init/example_snakemake/Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

Dockerfile runs as root: src/latch_cli/services/init/example_nfcore/Dockerfile

GapSeverity.MEDIUM Layer.HARDWARE score 0.225

Why: medium severity

#10

Very low test-to-source ratio

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/b86e022c-e18c-4345-8a54-afd7dc1b481d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b86e022c-e18c-4345-8a54-afd7dc1b481d/

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.