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.

ai-tech-community/aitcom

https://github.com/ai-tech-community/aitcom · scanned 2026-06-17 01:31 UTC (1 month, 2 weeks ago)

165 raw signals (0 security + 165 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -14.1 (diff) · 163 actionable findings from 1 signal source. 2 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 · 163 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 2 Medium 25 Low 44 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 163 Crowd 0 Layer: Api 1 Frontend 68 Hardware 2 Security 7 Cicd 1 Quality 84

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 52 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 next.config.js:14
info Commented-code block (7 lines) in src/app/api/mcp/route.ts:12
info Commented-code block (7 lines) in src/app/api/mcp/commission-tools.ts:5
info Commented-code block (5 lines) in src/app/[locale]/benchmark/dashboard/page.tsx…
info Commented-code block (6 lines) in src/scripts/backfill-impact-metadata.ts:210
info Commented-code block (9 lines) in src/scripts/seed-data/ownership.ts:37
info Commented-code block (6 lines) in src/scripts/seed-data/permits.ts:20
info Commented-code block (7 lines) in src/scripts/seed-data/capex.ts:10
info Commented-code block (7 lines) in src/server/api/routers/benchmark.ts:180
info Commented-code block (8 lines) in src/server/api/routers/hackathon.ts:274
info Commented-code block (7 lines) in src/server/api/routers/team-workspace.ts:1
info Commented-code block (10 lines) in src/server/api/routers/teams.ts:1

View all commented-out code findings →

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

3 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/skills/neon-postgres/refe… .claude/skills/neon-postgres/references/getting-s…:50
info Commented-code block (6 lines) in next.config.js:14
info Commented-code block (6 lines) in src/migrations/20260609d_challenge_team_confi…

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/fd48f480-92e5-41aa-ba51-7021b2fb58a2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fd48f480-92e5-41aa-ba51-7021b2fb58a2/

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.