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.

Rorqualx/Mugiwara-Kaizoku

https://github.com/Rorqualx/Mugiwara-Kaizoku · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

649 raw signals (0 security + 649 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 592 actionable findings from 1 signal source. 57 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 · 592 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 10 High 49 Medium 142 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 592 Crowd 0 Layer: Software 2 Frontend 167 Hardware 3 Security 67 Cicd 7 Quality 291 Api 55

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.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 11 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.

11 matching findings on this repo

low Old/deprecated-named symbol `fallbackToLegacy` in archive/ai-agent/orchestrator…
low Old/deprecated-named symbol `fallbackToLegacy` in archive/ai-agent/tools/wiki-s…
low Old/deprecated-named symbol `getCoverUrlLegacy` in packages/mangadex-ts-client/…
low Old/deprecated-named symbol `extractMetadataFromProviderLegacy` in src/componen…
low Old/deprecated-named symbol `MetadataConfigLegacy` in src/components/system/plu…
low Old/deprecated-named symbol `extractMetadataFromInfoboxLegacy` in src/server/pa…
low Old/deprecated-named symbol `fallbackToLegacy` in src/server/trpc/routers/manga…
low Old/deprecated-named symbol `fallbackToLegacy` in src/server/trpc/routers/manga…
low Old/deprecated-named symbol `fallbackToLegacy` in src/server/services/auto-labe…
low Old/deprecated-named symbol `fallbackToLegacy` in src/server/services/fandom/ad…
low Old/deprecated-named symbol `fallbackToLegacy` in src/server/services/fandom/ad…

View all legacy markers findings →

Commented-out code 179 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 eslint.config.mjs:194
info Commented-code block (5 lines) in tests/setup.ts:71
info Commented-code block (5 lines) in tests/server/trpc/routers/enrichment-pipeline…
info Commented-code block (5 lines) in tests/server/trpc/routers/enrichment-pipeline…
info Commented-code block (6 lines) in tests/server/trpc/routers/enrichment-pipeline…
info Commented-code block (5 lines) in tests/server/trpc/routers/enrichment-pipeline…
info Commented-code block (8 lines) in tests/server/services/library/indexerSearch/c…
info Commented-code block (5 lines) in tests/server/services/prowlarr/searchCache.te…
info Commented-code block (6 lines) in tests/server/services/packImport/file-scanner…
info Commented-code block (6 lines) in scripts/loadtest.js:29
info Commented-code block (5 lines) in scripts/fix-null-safety.ts:124
info Commented-code block (7 lines) in scripts/fix-ts7053-v2.ts:115

View all commented-out code findings →

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

12 matching findings on this repo

medium `dangerouslySetInnerHTML` used in a React component — scripts/security/config.t…
info TODO/FIXME marker in shipping code — src/server/config/feature-flags.ts:194
info TODO/FIXME marker in shipping code — src/server/services/search/configService.t…
info TODO/FIXME marker in shipping code — src/server/services/suwayomi/configService…
high Insecure pattern 'eval_used' in scripts/security/config.ts:224 scripts/security/config.ts:224
medium Insecure pattern 'dangerous_innerhtml' in scripts/security/config.ts:157 scripts/security/config.ts:157
medium Insecure pattern 'weak_hash' in scripts/security/config.ts:187 scripts/security/config.ts:187
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in eslint.config.mjs:194
info Commented-code block (7 lines) in src/components/manga/provider-bind-config.ts:…
low Old/deprecated-named symbol `MetadataConfigLegacy` in src/components/system/plu…
medium `fetch()` without try/.catch or AbortSignal — src/hooks/useDownloadClientConfig…

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/957e4458-4755-4f13-bddf-34a2f16d26e9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/957e4458-4755-4f13-bddf-34a2f16d26e9/

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.