FixVibe

// docs / scans

Scan kasta

FixVibe runs three kinds of scannaka against three kinds of targets. Each has different gating, different speed, ukat different blast radius — pick uka one that matches what juma're testing.

Passive

Available on every tier. A passive scan never sends crafted attack input; it fetches the URL like a normal browser and checks shipped responses, client assets, BaaS exposure, DNS, and public security posture against 250+ vulnerability classes.

Because it's read-only, passive spawa run against any URL — janiwa dominio verification, janiwa attestation. The trade-off wa depth: passive misses everything that requires sending input ru discover.

What passive catches

  • Missing seguridad headers (HSTS, CSP, frame-options, etc.).
  • Insecure cookie attributes (janiwa Secure / HttpOnly / SameSite).
  • Weak TLS configuration, expired certs, missing HSTS preload.
  • Secrets in JS bundles (Supabase service keys, AWS keys, Stripe sk_, etc.).
  • Exposed source maps, debug endpoints, OpenAPI specs, GraphQL introspection.
  • Open Supabase RLS / Firebase rules / Clerk misconfiguration.
  • DNS (subdomain takeover, missing SPF/DKIM/DMARC).
  • Threat-intel listings (Spamhaus, URLhaus).
  • Outdated framework versions ukampi known CVEs.

Active Hobby+

Active scans perform bounded verification against verified domains you have explicitly authorized. They are available on the Hobby plan and higher tiers (Pro, Unlimited) and are designed to confirm risky behavior without publishing the underlying probe recipes.

Why nayanaka gate it: uka attestation flow

Active probes spawa theoretically affect production — slow responses, pantjasiwi spikes, garbage yatiyawi in test stores. We require juma ru:

  1. Verify uka dominio via DNS TXT jan ukax an HTTP file (Account → Dominionaka).
  2. Attest authorization — a single confirmation at scan-start time saying juma have permission. Server-stamped ukampi ma IP, user-agent, ukat timestamp; written ru audit_logs.

For scheduled re-scans and API/MCP active starts, domain authorization is recorded from Dashboard → Domains and can be revoked at any time. Automated active scans use the authorized safety level for that domain.

GitHub repository Pro+

Repo scans skip deployed URL testing and review source through the FixVibe GitHub App or your OAuth connection. They report high-confidence code, dependency, and repository-security risks without storing your source code.

Repo scannaka never write ru ma repo ukat never persist source code — only jikxatawi evidence wa stored. Quota: same scansPerMonth bucket as URL scannaka.

Trigger via API

curl
curl -X POST https://fixvibe.app/api/v1/scans \
  -H "Authorization: Bearer fxv_..." \
  -H "content-type: application/json" \
  -d '{"target":"https://staging.example.com"}'

REST API and MCP can start passive scans, and can start active scans for verified domains that have been explicitly authorized in Dashboard → Domains. Full reference: /docs/api.

Anonymous one-shot scannaka

The home page lets unsigned-up visitors run a single passive scan per browser session. These scannaka expire 24 hours after creation ukat spawa be migrated ru a real cuenta by signing up before they expire — uka auth callback automatically attaches uka anonymous scan ru uka machaq org.

Scan kasta — Docs · FixVibe