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.

StorminRH/lgi-tools

https://github.com/StorminRH/lgi-tools · scanned 2026-06-16 01:14 UTC (2 months, 1 week ago)

365 raw signals (141 security + 224 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v2 · 231 actionable findings from 2 signal sources. 279 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 · 223 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 6 Medium 16 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 223 Crowd 0 Layer: Quality 190 Security 9 Api 1 Frontend 28 Hardware 1 Cicd 2

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 172 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 (5 lines) in eslint.config.mjs:6
info Commented-code block (6 lines) in next.config.ts:26
info Commented-code block (5 lines) in scripts/assert-route-classification.mjs:1
info Commented-code block (7 lines) in scripts/fallow-metrics.mjs:3
info Commented-code block (8 lines) in scripts/fallow-trial-log.mjs:3
info Commented-code block (7 lines) in convex/auth.config.ts:8
info Commented-code block (9 lines) in convex/schema.ts:23
info Commented-code block (5 lines) in convex/crons.ts:1
info Commented-code block (7 lines) in convex/skills.ts:4
info Commented-code block (6 lines) in convex/skillsSync.ts:9
info Commented-code block (7 lines) in convex/industryJobs.ts:5
info Commented-code block (5 lines) in convex/http.ts:1

View all commented-out code findings →

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

10 matching findings on this repo

medium Insecure pattern 'dangerous_innerhtml' in eslint.config.mjs:18 eslint.config.mjs:18
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:35
info Commented-code block (5 lines) in eslint.config.mjs:6
medium `fetch()` without try/.catch or AbortSignal — eslint.config.mjs:58
info Commented-code block (6 lines) in next.config.ts:26
info Commented-code block (7 lines) in convex/auth.config.ts:8
info Commented-code block (5 lines) in convex/convex.config.ts:1
info Commented-code block (6 lines) in src/config/feature-flags.ts:1
info Commented-code block (5 lines) in src/config/esi.ts:1
info Commented-code block (6 lines) in src/config/site-url.ts:1

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/0851fab9-1fb2-4be6-9cb9-35c8538c7366/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0851fab9-1fb2-4be6-9cb9-35c8538c7366/

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.