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.

shibanet0/datamitsu-config

https://github.com/shibanet0/datamitsu-config · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

99 raw signals (0 security + 99 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 21 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 71 Crowd 0 Layer: Api 1 Frontend 24 Hardware 3 Security 13 Cicd 5 Quality 25

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 15 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 vitest.setup.ts:3
info Commented-code block (5 lines) in scripts/oci-bundle-postprocess.ts:223
info Commented-code block (5 lines) in scripts/eslint-typegen.ts:1
info Commented-code block (5 lines) in src/apps/eslint/globals.d.ts:44
info Commented-code block (8 lines) in src/apps/eslint/plugins/n.ts:9
info Commented-code block (8 lines) in src/apps/eslint/plugins/unicorn.ts:6
info Commented-code block (8 lines) in src/apps/eslint/plugins/no-use-extend-native.…
info Commented-code block (5 lines) in src/apps/eslint/plugins/json.ts:12
info Commented-code block (8 lines) in src/apps/eslint/plugins/json-schema-validator…
info Commented-code block (10 lines) in src/apps/eslint/plugins/vanilla-extract.ts:9
info Commented-code block (8 lines) in src/apps/eslint/plugins/playwright.ts:9
info Commented-code block (11 lines) in src/apps/eslint/plugins/perfectionist.ts:60

View all commented-out code findings →

Config drift 14 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

low Stray `console.log` in TS/JS — scripts/generate-docs-setup-configs.ts:124
low Stray `console.log` in TS/JS — scripts/gen-tsconfig-md.ts:32
low Stray `console.log` in TS/JS — src/datamitsu-config/datamitsu.config.d.ts:1280
medium Insecure pattern 'node_child_process' in tsdown.config.eslint.ts:1 tsdown.config.eslint.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.knip.ts:1 tsdown.config.knip.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.commitlint.ts:1 tsdown.config.commitlint.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.cspell.ts:1 tsdown.config.cspell.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.ts:1 tsdown.config.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.oxfmt.ts:1 tsdown.config.oxfmt.ts:1
medium Insecure pattern 'node_child_process' in tsdown.config.prettier.ts:1 tsdown.config.prettier.ts:1
medium Insecure pattern 'node_child_process' in scripts/generate-docs-setup-configs.ts… scripts/generate-docs-setup-configs.ts:1
low Old/deprecated-named symbol `gomodguard_v2` in src/datamitsu-config/cmdSetup.ts…

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/43efdc51-38c7-4d9e-819e-995ea122281b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/43efdc51-38c7-4d9e-819e-995ea122281b/

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.