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.

zaitsu82/komine-crm-backend

https://github.com/zaitsu82/komine-crm-backend · scanned 2026-06-16 01:10 UTC (2 months, 1 week ago)

132 raw signals (0 security + 132 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 110 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

100.0% cov · 110 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 1 Medium 5 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 110 Crowd 0 Layer: Frontend 28 Network 2 Hardware 3 Security 3 Cicd 4 Quality 20 Api 50

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 Stray `console.log` in TS/JS — scripts/migrate-from-legacy.ts:103
low Stray `console.log` in TS/JS — scripts/check-legacy-data.ts:49
low Stray `console.log` in TS/JS — scripts/cleanup-legacy-data.ts:78
low Stray `console.log` in TS/JS — scripts/backfill-legacy-value-cleanup.ts:164
low Stray `console.log` in TS/JS — scripts/query-legacy.ts:48
low Old/deprecated-named symbol `withLegacy` in scripts/investigate-payment.ts:13
low Old/deprecated-named symbol `skipLegacy` in scripts/verify-migration.ts:87

View all legacy markers findings →

Commented-out code 10 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/`.

10 matching findings on this repo

info Commented-code block (5 lines) in scripts/verify-migration.ts:135
info Commented-code block (6 lines) in src/billings/billingService.ts:64
info Commented-code block (5 lines) in src/plots/controllers/getPlots.ts:234
info Commented-code block (6 lines) in src/plots/services/historyLabels.ts:455
info Commented-code block (7 lines) in src/auth/authController.ts:7
info Commented-code block (5 lines) in src/collective-burials/collectiveBurialImport…
info Commented-code block (5 lines) in src/validations/plotValidation.ts:220
info Commented-code block (5 lines) in src/validations/yuchoValidation.ts:13
info Commented-code block (6 lines) in src/masters/masterController.ts:1051
info Commented-code block (6 lines) in src/documents/permitPdfService.ts:118

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

info TODO/FIXME marker in shipping code — jest.config.js:25

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/a4d5a4df-2d4e-4ca2-93dd-8a85335ac25c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a4d5a4df-2d4e-4ca2-93dd-8a85335ac25c/

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.