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.

zulandar/railyard

https://github.com/zulandar/railyard · scanned 2026-06-16 01:13 UTC (2 months, 1 week ago)

140 raw signals (68 security + 72 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 47 actionable findings from 2 signal sources. 152 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 · 39 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 4 Medium 15 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 39 Crowd 0 Layer: Quality 28 Security 9 Software 3 Frontend 3 Cicd 4

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 charts/railyard/README.md

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 charts/railyard/README.md:316; move to env var / secrets manager.

charts/railyard/README.md:316

Possible secret in charts/railyard/ci/test-values-kind.yaml

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 charts/railyard/ci/test-values-kind.yaml:15; move to env var / secrets manager.

charts/railyard/ci/test-values-kind.yaml:15

Possible secret in charts/railyard/ci/test-values-kind.yaml

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 charts/railyard/ci/test-values-kind.yaml:21; move to env var / secrets manager.

charts/railyard/ci/test-values-kind.yaml:21

Possible secret in pkg/cli/cocoindex.go

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 pkg/cli/cocoindex.go:72; move to env var / secrets manager.

pkg/cli/cocoindex.go:72

Insecure pattern 'new_function_used' in internal/dashboard/assets/htmx.min.js:1

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

internal/dashboard/assets/htmx.min.js:1

Insecure pattern 'direct_innerhtml_assignment' in internal/dashboard/assets/htmx.min.js:1

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

internal/dashboard/assets/htmx.min.js:1

Insecure pattern 'insert_adjacent_html' in internal/dashboard/assets/htmx.min.js:1

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

internal/dashboard/assets/htmx.min.js:1

Insecure pattern 'domparser_html_parse' in internal/dashboard/assets/htmx.min.js:1

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

internal/dashboard/assets/htmx.min.js:1

Insecure pattern 'direct_innerhtml_assignment' in internal/dashboard/assets/sse.js:10

GapSeverity.MEDIUM Layer.SECURITY score 0.248

Why: medium severity · OWASP-class risk

internal/dashboard/assets/sse.js:10

#10

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/docker.yml:44

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/ebb6426d-ec66-4b73-9bc9-dd50160807a7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ebb6426d-ec66-4b73-9bc9-dd50160807a7/

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.