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.

SVM0N/csv-card-view

https://github.com/SVM0N/csv-card-view · scanned 2026-06-16 00:26 UTC (2 months, 2 weeks ago)

40 raw signals (0 security + 40 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 40 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 40 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 11 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 40 Crowd 0 Layer: Frontend 2 Security 9 Cicd 1 Quality 28

Exclude dismissed / FP Exclude test files

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.

Commented-out code 19 findings

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/`.

12 matching findings on this repo

info Commented-code block (6 lines) in main.ts:495
info Commented-code block (8 lines) in xlsx-to-csv-roundtrip.mjs:5
info Commented-code block (7 lines) in migrate-xlsx-to-csv.mjs:8
info Commented-code block (6 lines) in test-plugin-logic.mjs:876
info Commented-code block (8 lines) in esbuild.config.mjs:5
info Commented-code block (5 lines) in test-support/obsidian-stub.mjs:1
info Commented-code block (5 lines) in test-support/dom-env.mjs:3
info Commented-code block (6 lines) in src/add-entry-form.ts:26
info Commented-code block (8 lines) in src/utils.ts:220
info Commented-code block (6 lines) in src/modals.ts:104
info Commented-code block (5 lines) in src/travel-view.ts:132
info Commented-code block (6 lines) in src/view/stats.ts:1

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

info Commented-code block (8 lines) in esbuild.config.mjs:5

View all config drift findings →

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/92934823-cc12-42c8-8cda-b791310d87f9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/92934823-cc12-42c8-8cda-b791310d87f9/

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.