Customer FAQ

1) How do I activate my license?

Sign in at app.counterscarp.io. Purchases auto-link to your account. For CLI usage, set COUNTERSCARP_PRO_LICENSE or use your config file.

2) Why did my scan fail?

Most failures come from missing local tools (Slither/Foundry/Medusa), unsupported compiler versions, or malformed contract paths. See Troubleshooting.

3) How do refunds work?

Paid plans include a 14-day money-back guarantee. Contact contact@counterscarp.io with your account email and Stripe receipt.

4) How do I suppress false positives?

Use inline suppressions and config-based suppressions from Docs. Start with the minimum scope necessary and keep notes in your report output.

5) Does my code leave my machine?

CLI scans run locally. Webapp uploads are processed server-side for your scan session. Use CLI mode for strict local-only workflows.

6) Can I use this in CI/CD?

Yes. Use counterscarp generate-pipeline or copy templates from CI/CD docs.

7) What does “machine activation” mean?

It is the number of devices that can use paid CLI features at the same time for your tier.

8) Where can I report a bug?

Use GitHub bug report or email support.

9) How do I contact support?

Email contact@counterscarp.io. Include your scan ID, plan tier, and error output for fastest triage.

10) Is there a status page?

Yes. Visit counterscarp.io/status.html for current service health and incident notes.