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.

BaranziniLab/biorouter

https://github.com/BaranziniLab/biorouter · scanned 2026-06-17 01:21 UTC (1 month, 2 weeks ago)

172 raw signals (0 security + 172 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -16.3 (diff) · 156 actionable findings from 1 signal source. 16 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 · 156 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 3 Medium 24 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 156 Crowd 0 Layer: Software 2 Api 1 Frontend 71 Hardware 5 Security 13 Cicd 1 Quality 63

Exclude dismissed / FP Exclude test files

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

Possible secret in scripts/release.sh

GapSeverity.CRITICAL Layer.SECURITY score 1.000

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

Fix: Rotate the credential and remove it from in scripts/release.sh:63; move to env var / secrets manager.

scripts/release.sh:63

Runtime dotenv file present in repo: ui/desktop/.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 in ui/desktop/.env; move to env var / secrets manager.

ui/desktop/.env

Insecure pattern 'private_key_in_repo' in crates/biorouter/src/providers/gcpauth.rs:879

GapSeverity.CRITICAL Layer.SECURITY score 0.550

Why: critical severity · OWASP-class risk

crates/biorouter/src/providers/gcpauth.rs:879

Insecure pattern 'subprocess_shell_true' in crates/biorouter-mcp/src/computercontroller/platform/linux.rs:183

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

crates/biorouter-mcp/src/computercontroller/platform/linux.rs:183

Dockerfile pipes a remote installer into a shell

GapSeverity.HIGH Layer.HARDWARE score 0.375

Why: high severity

recipe-scanner/Dockerfile:35

Dockerfile pipes a remote installer into a shell

GapSeverity.HIGH Layer.HARDWARE score 0.375

Why: high severity

recipe-scanner/Dockerfile:41

Insecure pattern 'direct_innerhtml_assignment' in crates/biorouter-cli/static/script.js:62

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

crates/biorouter-cli/static/script.js:62

Insecure pattern 'node_child_process' in ui/desktop/scripts/unregister-deeplink-protocols.js:8

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

ui/desktop/scripts/unregister-deeplink-protocols.js:8

Insecure pattern 'node_child_process' in ui/desktop/scripts/fetch-llama-server.js:19

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

ui/desktop/scripts/fetch-llama-server.js:19

#10

Insecure pattern 'node_child_process' in ui/desktop/scripts/download-mingit.js:16

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

ui/desktop/scripts/download-mingit.js:16

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/637dc8c3-9ae2-4e19-bdb7-e4333af93073/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/637dc8c3-9ae2-4e19-bdb7-e4333af93073/

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.