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.

X-GIS/X-GIS

https://github.com/X-GIS/X-GIS · scanned 2026-06-16 01:02 UTC (2 months, 1 week ago)

1157 raw signals (0 security + 1157 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 1157 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 51 Low 234 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1157 Crowd 0 Layer: Frontend 207 Security 20 Cicd 2 Quality 928

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.

Legacy markers 8 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

8 matching findings on this repo

info Commented-code block (7 lines) in compiler/src/__tests__/legacy-filter-literal-…
info Commented-code block (5 lines) in compiler/src/__tests__/legacy-comparison-fiel…
low Old/deprecated-named symbol `invalidKeysLegacy` in compiler/src/convert/express…
low Old/deprecated-named symbol `useLegacy` in runtime/src/engine/source-manager.ts…
low Old/deprecated-named symbol `after_legacy` in runtime/src/engine/gpu/gpu-timer.…
low Old/deprecated-named symbol `clipLegacy` in runtime/src/engine/projection/camer…
low Old/deprecated-named symbol `clipLegacy` in runtime/src/engine/projection/polyg…
low Old/deprecated-named symbol `after_legacy` in runtime/src/engine/render/passes/…

View all legacy markers findings →

Commented-out code 864 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 vitest.config.ts:11
info Commented-code block (7 lines) in compiler/src/index.ts:33
info Commented-code block (5 lines) in compiler/src/__tests__/spec-coverage-notes.te…
info Commented-code block (7 lines) in compiler/src/__tests__/visibility-none-covera…
info Commented-code block (6 lines) in compiler/src/__tests__/polygon-outline-adjace…
info Commented-code block (6 lines) in compiler/src/__tests__/geojson-data-wrong-typ…
info Commented-code block (6 lines) in compiler/src/__tests__/interpolate-lab-hcl-de…
info Commented-code block (5 lines) in compiler/src/__tests__/text-field-multi-wrap-…
info Commented-code block (5 lines) in compiler/src/__tests__/partial-status-convers…
info Commented-code block (5 lines) in compiler/src/__tests__/text-field-numeric-cov…
info Commented-code block (6 lines) in compiler/src/__tests__/icon-image-step-zoom.t…
info Commented-code block (5 lines) in compiler/src/__tests__/literal-double-wrap-ex…

View all commented-out code findings →

Config drift 5 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.

5 matching findings on this repo

info Commented-code block (6 lines) in vitest.config.ts:11
info Commented-code block (6 lines) in playground/playwright.config.ts:24
info Commented-code block (9 lines) in playground/vite.config.ts:6
info Commented-code block (5 lines) in site/astro.config.mjs:19
info Commented-code block (6 lines) in runtime/vite.config.ts:6

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/f7b8653c-fc44-4475-b27f-253cf58a21b3/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f7b8653c-fc44-4475-b27f-253cf58a21b3/

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.