Flare
pricing
Sign up

//Blog

Notes from building a scanner for AI-written code.

What AI-generated apps actually get wrong, why conventional scanners don’t see it, and the bugs we shipped ourselves along the way.

Accuracy2026-08-042 min read

A leaked key isn’t a finding until you know it still works

Pattern-matching can’t tell a live credential from one you rotated last year. Calling both “critical” is how a scanner gets ignored.

Read
Engineering2026-08-042 min read

Your Anthropic key was being verified against OpenAI

A four-character oversight in a regex meant every Anthropic key was reported twice and checked against the wrong company’s API. Here’s how it surfaced.

Read
AI blind spots2026-08-042 min read

The secret that isn’t in your JavaScript

A Server Component passes an API key to a Client Component as a prop. The code is correct React, the key is in no .js file, and View Source is enough to read it.

Read
Accuracy2026-08-042 min read

Your .env.local is not a vulnerability

We shipped a check that reported a correctly-gitignored .env.local as a critical committed secret. It fired on almost every healthy repo. Here’s what went wrong.

Read
Flare

Find out what your app is leaking before anyone else does. Every finding mapped to CWE, OWASP & CVSS.

Product

  • Scan a URL
  • AI blind spots
  • Live-key verification
  • Coverage
  • Dashboard
  • Pricing

Resources

  • Docs
  • MCP server
  • API
  • CI & CLI
  • FAQ
  • Changelog
  • Status

Company

  • About
  • Blog
  • Ambassadors
  • Contact

Legal

  • Privacy
  • Terms
  • security.txt
  • llms.txt
  • Responsible disclosure

© 2026 Flare

Read-only checks against publicly reachable endpoints. Not a substitute for a full security review.