Skip to main content

Frequently Asked Questions

Common questions about FirePan, smart contract security, and our platform.

General

What is FirePan?

FirePan is an AI-assisted smart contract security platform. It provides repository-scoped surface scans, connected GitHub workflows, deeper hypothesis-driven analysis, and separately scoped human review.

How is FirePan different from traditional audits?

Traditional audits and FirePan answer different questions. A professional audit is a human assessment of an agreed code snapshot and threat model; FirePan makes automated repository checks repeatable as code changes.

TraditionalFirePan
Human review of an agreed scopeAutomated analysis of a repository state
Provider-specific delivery scheduleFast surface-scan triage
Formal engagement deliverableFindings and scan history in a dashboard
Researcher judgmentDeterministic detectors plus AI-assisted analysis

FirePan repository analysis is not a claim of 24/7 mempool, transaction, validator, bridge, or deployed-contract surveillance. Sentinel is a separate point-in-time EVM token scorecard.

What languages do you support?

Currently, we support:

  • Solidity repositories supported by the current parser and build path
  • Vyper repositories supported by the current parser and build path

Support for other smart contract languages (Cairo, Move) is planned.

Do you support all blockchain networks?

Source-code analysis is generally chain-agnostic for compatible Solidity and Vyper repositories, but FirePan does not infer that every chain-specific runtime behavior is covered. See the coverage page for the current boundary.


Security & Privacy

Is my code secure?

FirePan takes code security seriously. Access to private repositories and results is authenticated and authorized. For exact collection, processing, retention, and third-party-provider terms, use the current Privacy Policy and your written service agreement rather than relying on a marketing summary.

Do you store my source code?

Data handling depends on the product and engagement. The current Privacy Policy is the controlling public description; enterprise or audit engagements may add written terms.

Can I use FirePan for private repositories?

Yes. Our GitHub App requests only the permissions needed to read your code. Private repository contents are never exposed.

Who can see my scan results?

Authenticated results are tied to an organization and protected by application access controls. The service may use subprocessors described in the Privacy Policy; do not infer a broader confidentiality or model-training promise than the applicable written terms provide.


Getting Started

How do I get started?

  1. Sign up at app.firepan.com
  2. Install our GitHub App
  3. Connect your repositories
  4. Configure the repositories and events you want analyzed

See our Quickstart for detailed instructions.

How can I try FirePan?

Book a demo and we'll walk you through the platform with a live scan of your repositories.


Scans & Audits

What's the difference between a scan and an audit?

ScanAudit
Fast first-pass triageRepository-dependent runtime
Deterministic detectors + optional AI verificationMulti-pass hypothesis-driven analysis
Small bounded workloadWorkload varies by repository and analysis path
Quick triageComprehensive review
Included in all plansLimited per plan

How often should I scan?

We recommend:

  • Every PR - Catch issues before they merge
  • Daily - For active development
  • Weekly - For stable codebases

What does the risk score mean?

ScoreLevelMeaning
70-100CriticalMajor issues, investigate immediately
50-69HighSignificant findings, address soon
25-49MediumSome issues worth noting
0-24LowMinor findings, typical for mature code

Why do battle-tested contracts show vulnerabilities?

Pattern-based scanning is intentionally sensitive. Well-audited code like OpenZeppelin may show findings that are:

  • Intentional design decisions
  • False positives from regex limitations
  • Patterns that look risky but are properly mitigated

Always verify findings before acting on them.


Pricing & Billing

How are scans counted?

A scan is counted when:

  • You manually trigger a scan
  • A PR check runs
  • A scheduled scan executes

What happens if I exceed my limits?

Usage above a plan's published limits is handled under the current checkout or written order terms. Contact sales for a current quote rather than relying on an undocumented overage amount.

Can I cancel anytime?

Yes. Cancel anytime from your dashboard. You'll retain access until the end of your billing period.

Do you offer refunds?

Refund eligibility is governed by the current Terms of Service and any written order form.


Technical

Does FirePan work with CI/CD?

GitHub-connected repository workflows are the supported hosted path. API or command-line availability depends on the account and deployment; confirm the current integration before designing a blocking CI gate.

See CI/CD Integration for details.

Can I run FirePan locally?

Internal and engagement-specific command-line tooling exists, but the public unauthenticated path is the GitHub repository surface scan. Do not assume a package name or distribution channel without checking the current installation guide.

Does FirePan work offline?

FirePan requires an internet connection for AI-powered analysis. The CLI authenticates with your FirePan account and uses our API for scanning.


Enterprise

Do you offer enterprise plans?

Enterprise scope is quote-based and can include repository limits, review support, custom detector work, or service commitments when they are written into the order form.

Contact sales for details.

Can you run in our cloud?

Deployment architecture is engagement-specific. Contact sales to confirm whether a managed, dedicated, or customer-hosted arrangement is available for your requirements.

Do you offer security retainers?

Yes. After a boutique audit, you can retain our security team for:

  • Ongoing review of changes
  • Rapid response to incidents
  • Security consultation

Still Have Questions?