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.

shiroha-a/mk

https://github.com/shiroha-a/mk · scanned 2026-06-16 00:11 UTC (2 months, 2 weeks ago)

248 raw signals (0 security + 248 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 226 actionable findings from 1 signal source. 22 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 226 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 2 Medium 35 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 226 Crowd 0 Layer: Frontend 3 Network 4 Hardware 16 Security 21 Cicd 3 Quality 179

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 146 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 (5 lines) in tests/dropin/test_swap_setup.py:180
info Commented-code block (8 lines) in tests/dropin_frontend/cypress/cypress.config.…
info Commented-code block (5 lines) in tests/dropin_frontend/cypress/support/setup.t…
info Commented-code block (9 lines) in tests/dropin_frontend/cypress/e2e/reply_chain…
info Commented-code block (9 lines) in tests/dropin_frontend/cypress/e2e/visibility.…
info Commented-code block (7 lines) in tests/bench/common/seed.py:23
info Commented-code block (6 lines) in tests/queue-bench/common/driver_inbound.py:78
info Commented-code block (5 lines) in tests/queue-bench/common/seed.py:245
info Commented-code block (8 lines) in tests/playwright/playwright.config.ts:27
info Commented-code block (9 lines) in tests/playwright/global-setup.ts:6
info Commented-code block (7 lines) in tests/playwright/fixtures/timeline.ts:3
info Commented-code block (5 lines) in tests/playwright/fixtures/files.ts:29

View all commented-out code findings →

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

2 matching findings on this repo

info Commented-code block (8 lines) in tests/dropin_frontend/cypress/cypress.config.…
info Commented-code block (8 lines) in tests/playwright/playwright.config.ts:27

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/4301181b-f7e7-44e0-a59f-4211f4fd0257/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4301181b-f7e7-44e0-a59f-4211f4fd0257/

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.