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.

berkayturanci/ai-jury

https://github.com/berkayturanci/ai-jury · scanned 2026-06-17 01:39 UTC (1 month, 2 weeks ago)

38 raw signals (0 security + 38 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.9 (diff) · 33 actionable findings from 1 signal source. 5 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 · 33 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 9 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 33 Crowd 0 Layer: Security 6 Cicd 1 Quality 26

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 61.8/100 with 77.8% coverage. It contains 2277 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 38 findings — concentrated in quality (29), security (6), cicd (3). Risk profile is high: 1 critical, 1 high, 11 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 16 of 33 actionable findings. 38 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in benchmark/sweep.py:52

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

benchmark/sweep.py:52 Tls verify false

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: docs/skill.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

docs/skill.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skill/ai-jury/SKILL.md

skill/ai-jury/SKILL.md VerificationSkill file

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

3 files, 3 locations

.github/workflows/pages.yml

.github/workflows/publish.yml

.github/workflows/scorecard.yml

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/app.js:120

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

website/app.js:120 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/coverage-report.html:176

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

website/coverage-report.html:176 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/coverage.html:192

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

website/coverage.html:192 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in website/docs.html:147

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

website/docs.html:147 Direct innerhtml assignment

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 54 placeholder/mock markers across 14 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 59 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: src/ai_jury/orchestrator.py:run_jury, src/ai_jury/orchestrator.py:review_diff This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

duplicatesduplication

low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: src/ai_jury/adapters.py:available, src/ai_jury/adapters.py:available, src/ai_jury/adapters.py:available This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why the…

4 occurrences

repo-level (4 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: src/ai_jury/adapters.py:build_argv, src/ai_jury/adapters.py:build_argv, src/ai_jury/adapters.py:build_argv, src/ai_jury/adapters.py:build_argv This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hy…

duplicatesduplication

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `parse_v2` in tests/test_cov_orchestrator.py:553

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Complexity conf 1.00 Very large file: src/ai_jury/cli.py (1567 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

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/881478f9-7ca1-4fe0-95a7-844b23012db1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/881478f9-7ca1-4fe0-95a7-844b23012db1/

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.