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.

vultisig/vultisig-windows

https://github.com/vultisig/vultisig-windows · scanned 2026-06-16 00:54 UTC (2 months, 1 week ago)

303 raw signals (0 security + 303 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 161 actionable findings from 1 signal source. 142 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 · 161 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 10 High 3 Medium 29 Low 82 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 161 Crowd 0 Layer: Frontend 49 Security 19 Cicd 2 Quality 91

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

2 matching findings on this repo

low Old/deprecated-named symbol `IMessageLegacy` in core/inpage-provider/popup/view…
low Old/deprecated-named symbol `IMessageLegacy` in core/inpage-provider/popup/view…

View all legacy markers findings →

Commented-out code 29 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 (8 lines) in eslint.config.mjs:131
info Commented-code block (6 lines) in clients/desktop/src/notifications/DesktopNoti…
info Commented-code block (5 lines) in clients/extension/tests/e2e/specs/dump-vault-…
info Commented-code block (7 lines) in clients/extension/src/inpage/index.ts:3
info Commented-code block (5 lines) in clients/extension/src/inpage/providers/xdefiK…
info Commented-code block (5 lines) in clients/extension/src/inpage/providers/keplrC…
info Commented-code block (5 lines) in clients/extension/src/inpage/providers/cardan…
info Commented-code block (5 lines) in clients/extension/src/inpage/providers/statio…
info Commented-code block (5 lines) in clients/extension/src/inpage/providers/sui/si…
info Commented-code block (7 lines) in clients/extension/src/inpage/providers/cosmos…
info Commented-code block (7 lines) in clients/extension/src/content/index.ts:4
info Commented-code block (6 lines) in core/ui/vault/send/addresses/components/Manag…

View all commented-out code findings →

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

6 matching findings on this repo

info TODO/FIXME marker in shipping code — core/ui/vault/deposit/utils/getDepositForm…
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/rules/assert.md .claude/rules/assert.md:30
high Agent instruction/config may expose a secret: .claude/skills/i18n-workflow/SKIL… .claude/skills/i18n-workflow/SKILL.md:58
info Commented-code block (8 lines) in eslint.config.mjs:131
info Commented-code block (6 lines) in core/ui/vault/deposit/utils/getDepositFormCon…

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/f73003a2-3c67-45a1-b59b-66924ba5f062/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f73003a2-3c67-45a1-b59b-66924ba5f062/

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.