ZToolsCenter/ZTools

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.

35 of your 176 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 8.59s · analysis 33.23s · 19.9 MB · GitHub API rate-limit (preflight)

https://github.com/ZToolsCenter/ZTools · scanned 2026-06-05 14:58 UTC (5 days, 4 hours ago) · 10 languages

458 raw signals (164 security + 294 graph) 33rd percentile · Typescript · medium (20-100K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 4 hours ago · v2 · 230 actionable findings from 2 signal sources. 81 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 · 135 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	51.4	0.25	12.85
`testing_score`	45.0	0.20	9.00
`documentation_score`	91.7	0.15	13.76
`practices_score`	79.0	0.15	11.85
`code_quality`	48.0	0.10	4.80
Overall		1.00	65.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 31 Medium 28 Low 143 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 95 System graph 135 Crowd 0 Layer: Quality 28 Software 106 Security 7 Cicd 4 Api 1 Frontend 84

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 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (7 lines) in src/main/utils/lanzou.ts:70

View all commented-out code findings →

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

4 matching findings on this repo

low File has no detected symbols: electron.vite.config.ts
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: internal-plugins/setting/vite.config.ts
low File has no detected symbols: internal-plugins/setting/uno.config.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/fcb547a4-9bf8-4178-a565-016562e09987/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fcb547a4-9bf8-4178-a565-016562e09987/

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.