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.

anuraagkolli/invariance

https://github.com/anuraagkolli/invariance · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

161 raw signals (0 security + 161 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -13.2 (diff) · 161 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 161 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 33 Medium 38 Low 37 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 161 Crowd 0 Layer: Frontend 12 Hardware 2 Security 5 Quality 92 Api 50

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 50 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 (7 lines) in packages/cli/src/analysis/roles/cluster.ts:1
info Commented-code block (6 lines) in packages/design/src/server.ts:1
info Commented-code block (9 lines) in packages/design/src/headless.ts:3
info Commented-code block (5 lines) in packages/design/src/fonts/loader.ts:16
info Commented-code block (6 lines) in packages/design/src/compiler/contrast.ts:32
info Commented-code block (5 lines) in packages/design/src/compiler/tokens.ts:41
info Commented-code block (5 lines) in packages/design/src/compiler/roles.ts:62
info Commented-code block (7 lines) in packages/design/src/compiler/compiler-values.…
info Commented-code block (7 lines) in packages/design/src/compiler/cluster.ts:6
info Commented-code block (6 lines) in packages/design/src/context/provider.tsx:128
info Commented-code block (6 lines) in packages/design/src/context/use-current-page.…
info Commented-code block (6 lines) in packages/design/src/context/apply-reconcile.t…

View all commented-out code findings →

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

7 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
info Commented-code block (6 lines) in packages/design/src/config/upgrade.ts:11
medium `fetch()` without try/.catch or AbortSignal — apps/control-plane/test/design-co…
info Commented-code block (6 lines) in apps/nebula/next.config.js:24
info Commented-code block (9 lines) in apps/nebula/src/lib/invariance-config.ts:54
info Commented-code block (5 lines) in apps/nebula/src/lib/dev-config.ts:3
low Unused endpoint: GET /v1/apps/:appId/design-config

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/71ba199a-0e11-4e7d-bf03-83c9dd3a2206/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/71ba199a-0e11-4e7d-bf03-83c9dd3a2206/

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.