tsz-org/tsz

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.

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

https://github.com/tsz-org/tsz · scanned 2026-06-05 15:24 UTC (5 days, 2 hours ago) · 10 languages

1638 raw signals (52 security + 1586 graph) 11/13 scanners ran 32nd percentile · Rust · large (100-500K LoC) System graph score 60 (higher by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 739 actionable findings from 2 signal sources. 106 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 · 728 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	26.0	0.20	5.20
`documentation_score`	66.0	0.15	9.90
`practices_score`	67.0	0.15	10.05
`code_quality`	50.0	0.10	5.00
Overall		1.00	64.2

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 5 Medium 18 Low 701 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 11 System graph 728 Crowd 0 Layer: Software 55 Quality 656 Cicd 4 Api 1 Frontend 13 Network 4 Hardware 3 Security 3

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 2 findings

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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low File has no detected symbols: crates/tsz-core/src/lib-assets-stripped/decorator…

View all legacy markers findings →

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

9 matching findings on this repo

info Commented-code block (7 lines) in scripts/emit/src/runner.ts:415
info Commented-code block (5 lines) in scripts/emit/src/baseline-parser.ts:87
info Commented-code block (5 lines) in scripts/conformance/query-conformance.py:441
info Commented-code block (5 lines) in scripts/arch/arch_guard_shared.py:237
info Commented-code block (12 lines) in scripts/arch/test_arch_guard.py:673
info Commented-code block (5 lines) in scripts/arch/arch_guard_config.py:70
info Commented-code block (6 lines) in crates/tsz-wasm/js/tsz.js:2
info Commented-code block (5 lines) in crates/tsz-website/.eleventy.js:14
info Commented-code block (6 lines) in crates/tsz-website/src/_data/loc.js:3

View all commented-out code findings →

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

5 matching findings on this repo

low File has no detected symbols: scripts/arch/arch_guard_config.py
low Very large file: crates/tsz-core/src/config/mod.rs (1912 lines)
low Very large file: crates/tsz-core/src/config/parse.rs (1514 lines)
low Very large file: crates/tsz-core/src/config/tests/module_resolution.rs (1431 li…
info Commented-code block (5 lines) in scripts/arch/arch_guard_config.py:70

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/3519fd32-b5d6-43ae-a54f-3d5bb4cbb164/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3519fd32-b5d6-43ae-a54f-3d5bb4cbb164/

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.