quarkdown

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.

https://github.com/iamgio/quarkdown.git · scanned 2026-05-16 13:31 UTC (1 day, 8 hours ago) · 10 languages

107 findings (11 legacy + 96 scanner) Scanner says 82 (lower by 2)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 day, 5 hours ago · v1 · 102 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

Score breakdown â 2026-05-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	93.3	0.25	23.32
`testing_score`	90.0	0.20	18.00
`documentation_score`	85.0	0.15	12.75
`practices_score`	75.0	0.15	11.25
`code_quality`	80.0	0.10	8.00
Overall		1.00	79.3

Calibrated penalty buckets (security_score): docker: 2.7 Â· threat: 4.0

Severity distribution — click a segment to filter

Active filters: source: legacy × excluding tests × Reset all

Scan summary Repository scanned at 81.5/100 with 88.9% coverage. It contains 1980 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 96 findings — concentrated in software (50), cicd (31), frontend (7). Risk profile is high: 0 critical, 4 high, 23 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 6 of 102 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high Legacy security path_traversal conf 0.80 [SEC013] Path Traversal — User Input in File Path: User-controlled input used in file path without sanitization. Allows reading arbitrary files.

Use os.path.realpath() and verify the path starts with your expected base directory. Use secure_filename() for uploads.

quarkdown-lsp/src/main/kotlin/com/quarkdown/lsp/QuarkdownTextDocumentService.kt:107 path_traversallegacy

high Legacy software ssrf conf 1.00 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches.

Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400) Or use a server-side proxy (Imgproxy / serve-files-only-from-S3) that isolates outbound network access from the request h…

quarkdown-core/src/main/kotlin/com/quarkdown/core/rendering/NodeRenderer.kt:43 ssrflegacy

quarkdown-core/src/main/kotlin/com/quarkdown/core/util/URLUtils.kt:23 ssrflegacy

quarkdown-core/src/main/kotlin/com/quarkdown/core/parser/InlineTokenParser.kt:185 ssrflegacy

high Legacy cicd docker conf 0.76 Dockerfile copies broad context with incomplete .dockerignore

COPY . or ADD . is safer when .dockerignore excludes secrets, git history, keys, and generated artifacts.

Dockerfile:15 dockerlegacy

low Legacy cicd docker conf 0.72 .dockerignore misses sensitive defaults

.dockerignore exists but does not cover common secret or VCS patterns.

.dockerignore dockerlegacy

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/fdbc0f20-2bc8-421b-9def-a2e59a60a1dd/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fdbc0f20-2bc8-421b-9def-a2e59a60a1dd/

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.