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.

Avvacumrechevoi/yasnanegotiations

https://github.com/Avvacumrechevoi/yasnanegotiations · scanned 2026-06-17 01:19 UTC (1 month, 2 weeks ago)

181 raw signals (0 security + 181 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -37.6 (diff) · 176 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 · 176 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 2 Medium 37 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 176 Crowd 0 Layer: Frontend 28 Data 1 Security 22 Cicd 2 Quality 118 Api 5

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.

Legacy markers 7 findings

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.

7 matching findings on this repo

low Old/deprecated-named symbol `themesWithoutLegacy` in scripts/build-content.mjs:…
low Old/deprecated-named symbol `questionsLegacy` in docs/games/duel/content.bundle…
low Old/deprecated-named symbol `tryLegacy` in docs/games/duel/duel.js:103
low Old/deprecated-named symbol `questionsLegacy` in docs/games/duel/trivia-bank.js…
low Old/deprecated-named symbol `questionsLegacy` in docs/preview/games/duel/conten…
low Old/deprecated-named symbol `tryLegacy` in docs/preview/games/duel/duel.js:103
low Old/deprecated-named symbol `questionsLegacy` in docs/preview/games/duel/trivia…

View all legacy markers findings →

Commented-out code 74 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 (12 lines) in tests/nav-responsive.spec.mjs:3
info Commented-code block (7 lines) in tests/custom-yasna.spec.mjs:3
info Commented-code block (6 lines) in tests/smoke.spec.mjs:7
info Commented-code block (5 lines) in scripts/serve.mjs:1
info Commented-code block (8 lines) in scripts/validate-content.mjs:4
info Commented-code block (6 lines) in scripts/build-content.mjs:4
info Commented-code block (8 lines) in scripts/build.mjs:8
info Commented-code block (8 lines) in scripts/convert-unsupported.mjs:6
info Commented-code block (7 lines) in server/content-publish.js:16
info Commented-code block (6 lines) in server/leaderboard.js:1
info Commented-code block (5 lines) in server/content-fetch.js:9
info Commented-code block (10 lines) in server/auth-telegram.js:1

View all commented-out code 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/20a7bcd9-20dc-439e-9621-3d379eaa5510/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/20a7bcd9-20dc-439e-9621-3d379eaa5510/

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.