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.

Doguserkivac09/BistAi

https://github.com/Doguserkivac09/BistAi · scanned 2026-06-17 01:27 UTC (1 month, 2 weeks ago)

322 raw signals (0 security + 322 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 322 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 140 Medium 122 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 322 Crowd 0 Layer: Frontend 42 Security 10 Quality 131 Api 139

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 7 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/`.

7 matching findings on this repo

info Commented-code block (5 lines) in app/api/cron/scan-cache/route.ts:29
info Commented-code block (5 lines) in app/api/uzun-vade-firsatlar/route.ts:99
info Commented-code block (5 lines) in app/makro/page.tsx:167
info Commented-code block (5 lines) in lib/signals.ts:922
info Commented-code block (5 lines) in lib/news-impact.ts:375
info Commented-code block (7 lines) in lib/fundamental-health.ts:78
info Commented-code block (5 lines) in .claude/hooks/gsd-context-monitor.js:2

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

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/get-shit-done/workflows/p… .claude/get-shit-done/workflows/plan-phase.md:460
medium Agent authority lacks a verifier contract: .claude/get-shit-done/references/pla… .claude/get-shit-done/references/planning-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/69b2a03d-62ad-4191-9954-764151e98abb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/69b2a03d-62ad-4191-9954-764151e98abb/

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.