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.

saltbo/zpan

https://github.com/saltbo/zpan · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

1434 raw signals (0 security + 1434 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 11 High 1274 Medium 28 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1422 Crowd 0 Layer: Frontend 36 Network 2 Hardware 4 Security 19 Cicd 3 Quality 76 Api 1282

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 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 Old/deprecated-named symbol `sub_storage_legacy` in server/adapters/repos/quota…

View all legacy markers findings →

Commented-out code 44 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 playwright.config.ts:4
info Commented-code block (6 lines) in shared/content-disposition.ts:3
info Commented-code block (6 lines) in scripts/lint-spec.mjs:4
info Commented-code block (6 lines) in workers/bootstrap.ts:23
info Commented-code block (9 lines) in server/auth.integration.test.ts:758
info Commented-code block (5 lines) in server/auth.ts:495
info Commented-code block (5 lines) in server/composition.ts:1
info Commented-code block (5 lines) in server/app.ts:104
info Commented-code block (5 lines) in server/entry-node.ts:30
info Commented-code block (5 lines) in server/adapters/repos/matter.ts:243
info Commented-code block (5 lines) in server/adapters/gateways/image-upload.ts:38
info Commented-code block (5 lines) in server/http/users.ts:50

View all commented-out code findings →

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

info Commented-code block (5 lines) in playwright.config.ts:4
info Commented-code block (8 lines) in server/usecases/image-hosting/config.ts:1
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: PUT /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: POST /api/site/email/test-messages (server/http/site/email-conf…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: GET /api/site/email (server/http/site/email-config.integration.…
high Dangling fetch: PUT /api/site/email (server/http/site/email-config.integration.…

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/4992bb9c-0160-41f3-915d-964087a208fe/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4992bb9c-0160-41f3-915d-964087a208fe/

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.