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.

ssiddharthsoni-spec/irongate2

https://github.com/ssiddharthsoni-spec/irongate2 · scanned 2026-06-16 00:21 UTC (2 months, 2 weeks ago)

386 raw signals (0 security + 386 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 354 actionable findings from 1 signal source. 32 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 · 354 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 55 Medium 42 Low 149 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 354 Crowd 0 Layer: Software 3 Frontend 77 Network 2 Hardware 5 Security 27 Cicd 3 Quality 142 Api 95

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.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `_generateFakeLegacy` in apps/extension/src/content…

View all legacy markers findings →

Commented-out code 83 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 eslint.config.js:24
info Commented-code block (5 lines) in v0.3-foundation/src/core/dedupe/resolver.ts:6
info Commented-code block (5 lines) in v0.3-foundation/src/core/detectors/interface.…
info Commented-code block (5 lines) in v0.3-foundation/src/contracts/messages.ts:4
info Commented-code block (5 lines) in v0.3-foundation/src/contracts/evidence.ts:4
info Commented-code block (7 lines) in apps/api/src/index.ts:399
info Commented-code block (7 lines) in apps/api/src/monitoring/query-anomaly-detecto…
info Commented-code block (7 lines) in apps/api/src/monitoring/breach-detection.ts:1
info Commented-code block (8 lines) in apps/api/src/monitoring/security-alerts.ts:1
info Commented-code block (6 lines) in apps/api/src/middleware/jwt-revocation.ts:101
info Commented-code block (5 lines) in apps/api/src/proxy/llm-router.ts:10
info Commented-code block (5 lines) in apps/api/src/lib/token-encryption.ts:12

View all commented-out code findings →

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

6 matching findings on this repo

low Stray `console.log` in TS/JS — apps/extension/vite.config.ts:70
low Stray `console.log` in TS/JS — apps/vscode-extension/esbuild.config.js:21
low Node manifest has dependencies but no lockfile: packages/config/package.json packages/config/package.json
high Agent instruction/config may expose a secret: .claude/skills/irongate-tester.md .claude/skills/irongate-tester.md:64
info Commented-code block (6 lines) in eslint.config.js:24
info Commented-code block (5 lines) in apps/extension/src/managed-config.ts:53

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/cb4cec86-4847-42c8-972c-a7d659966e64/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cb4cec86-4847-42c8-972c-a7d659966e64/

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.