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.

skapxd/eslint-opinionated

https://github.com/skapxd/eslint-opinionated · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

55 raw signals (0 security + 55 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 35 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 11 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 35 Crowd 0 Layer: Api 1 Frontend 3 Security 7 Cicd 3 Quality 21

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 15 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 src/rules/no-floating-promises.ts:3
info Commented-code block (7 lines) in src/rules/no-anonymous-condition.ts:11
info Commented-code block (5 lines) in src/rules/untrusted-module-requires-adapter.t…
info Commented-code block (6 lines) in src/shared/configs/create-shared-configs.ts:26
info Commented-code block (5 lines) in src/shared/configs/type-driven-rules.ts:3
info Commented-code block (5 lines) in src/constants/default-export-allowed-file-pat…
info Commented-code block (6 lines) in src/utils/ast/is-literal-guard-comparison.ts:7
info Commented-code block (5 lines) in src/utils/options/get-strict-tsconfig-options…
info Commented-code block (5 lines) in src/utils/react/get-state-shape-smell.ts:5
info Commented-code block (5 lines) in src/utils/react/is-expression-arrow-function.…
info Commented-code block (5 lines) in src/utils/imports/get-declared-alias-targets.…
info Commented-code block (5 lines) in src/utils/rule-authoring/wrap-tseslint-rule.t…

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 TODO/FIXME marker in shipping code — src/nest/create-nest-configs.ts:41
info Commented-code block (6 lines) in src/shared/configs/create-shared-configs.ts:26
info Commented-code block (5 lines) in src/shared/configs/type-driven-rules.ts:3
info Commented-code block (5 lines) in src/utils/options/get-strict-tsconfig-options…
info Commented-code block (7 lines) in src/nest/create-nest-configs.ts:30

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/656ad7e0-7f45-441e-8f06-855fb2020236/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/656ad7e0-7f45-441e-8f06-855fb2020236/

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.