Troubleshooting

Platform checks

• Verification fails: confirm the authoritative TXT record and wait for negative-cache expiry.
• Audit stays queued: check service status and available plan capacity before retrying.
• Score changed: compare profile, modules, coverage, ruleset, scoring version, and baseline.
• Alert does not arrive: test the channel and confirm its saved destination and severity threshold.

Supabase Deep Scan checks

• Project is not detected: enter the project URL and anonymous key manually.
• Scan cannot start: confirm that the Platform domain is verified.
• Unexpected data access: reproduce with the anonymous role and inspect the intended RLS policy.
• Wrong project is linked: unlink it before connecting the correct project.

CLI checks

• vice is missing: verify the global npm binary path or use npx vice-security.
• Browser checks fail: confirm Chromium and compatible runtime dependencies are available.
• An unexpected file is scanned: inspect the project root and .viceignore.
• The audit is slow: review repository size, Git history, dependencies, and custom modules.

GitHub Action checks

• PR comment fails: grant pull-requests: write for the trusted event.
• SARIF upload fails: grant security-events: write and confirm Code Scanning availability.
• Badge update fails: grant contents: write and review branch protection.
• Gate changed unexpectedly: compare Action version, configuration, baseline, and report coverage.

Prepare a useful support report

Include the VICE surface, exact command or workflow step, package or Action version, engine and ruleset versions, coverage status, sanitized error, and operating environment.