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.

anuarissa/axie-duel

https://github.com/anuarissa/axie-duel · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

80 raw signals (0 security + 80 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 19 Low 32 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 77 Crowd 0 Layer: Frontend 12 Hardware 3 Security 4 Quality 58

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 23 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 scripts/smoke-pvp-chain.mjs:1
info Commented-code block (6 lines) in scripts/smoke-pve-statefilter.mjs:1
info Commented-code block (6 lines) in scripts/smoke-pve-trap.mjs:1
info Commented-code block (6 lines) in trailer/capture/gen-text-pngs.py:1
info Commented-code block (7 lines) in apps/api/tests/tournament.e2e.test.ts:149
info Commented-code block (7 lines) in apps/api/src/services/AxieCardSyncService.ts:…
info Commented-code block (5 lines) in apps/api/src/services/AccountService.ts:64
info Commented-code block (9 lines) in apps/api/src/services/AxieGraphQLService.ts:1…
info Commented-code block (5 lines) in apps/api/src/services/StarterDeckService.ts:4…
info Commented-code block (6 lines) in apps/api/src/routes/deck.routes.ts:59
info Commented-code block (7 lines) in apps/api/src/routes/internal.routes.ts:162
info Commented-code block (8 lines) in apps/game-server/src/index.ts:22

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

low Node manifest has dependencies but no lockfile: packages/eslint-config/package.… packages/eslint-config/package.json

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/9a9a1668-4dfd-4973-9f6f-7d4368b9febf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9a9a1668-4dfd-4973-9f6f-7d4368b9febf/

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.