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.
Sign up free Scan another repo

quarkdown

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
Combined
76.2
/100
Repobility
71
6 legacy
9-layer
82
88.9% cov · 96 gaps
Critical
0
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 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: excluding tests × Reset all
Severity: Critical 0 High 9 Medium 23 Low 67 Source: Legacy 6 9-layer 96 Crowd 0 Layer: Cicd 33 Software 53 Security 2 Api 1 Frontend 7 Hardware 4 Quality 2

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 1 finding
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
1 matching finding on this repo
  • medium `fetch()` without try/.catch or AbortSignal — quarkdown-html/src/main/typescrip…
View all fragile runtime findings →
Commented-out code 1 finding
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
1 matching finding on this repo
  • info Commented-code block (6 lines) in quarkdown-html/src/test/e2e/page-format/scope…
View all commented-out code findings →
Config drift 3 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
3 matching findings on this repo
  • low File has no detected symbols: quarkdown-html/playwright.config.ts
  • low File has no detected symbols: quarkdown-html/vitest.config.ts
  • low File has no detected symbols: quarkdown-html/src/test/e2e/paragraph/localized-c…
View all config drift findings →
{# ── 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.