Understand your code. Protect what you build.

Know What Your AI Built.

See how the parts of your project fit together, what needs attention, and what changed after a fix.

  • Reads the code, never runs it
  • No sign-in
  • Shows what it couldn't check

This preview uses made-up sample projects only. Nothing to upload.

Example reportSynthetic sample
A real Ctrlflip report on a made-up sample project (Corner Shop, version 1), prepared on this server.

How it works

One simple loop, every time your AI builder changes something

Inspect a version, fix what matters, then inspect the next version to see what really changed.

  1. Choose a project

    Today: a made-up sample. Your own projects come after their security checks pass.

  2. Inspect

    Ctrlflip reads the committed code. Nothing in the project is run.

  3. Understand

    See what needs attention first, the evidence, and what couldn't be checked.

  4. Copy fix instructions

    Preview the text, then paste it into Claude, ChatGPT, Cursor or your AI builder.

  5. Inspect again

    After your AI builder changes the code, inspect the new version.

  6. Compare

    See what is confirmed fixed, what is new, and what couldn't be confirmed.

Today's checks

What Ctrlflip checks today

These checks run on every sample inspection on this website. Each report says which files it read; anything it could not read is listed under “Couldn't check”, never counted as clean.

  • Reading the committed files
  • Reading the JavaScript/TypeScript code
  • Tracing how files connect to each other
  • Approved architecture rules
  • Circular dependencies
  • Copied code
  • Passwords and access keys in the code
  • One package in several versions
  • Tests and controls changed by the candidate

The last check runs when two versions are compared. Not run on this website yet: known vulnerabilities in third-party packages (it needs an advisory database), capability claims, and declared ownership of responsibilities (it needs owners you declare). Ctrlflip reads code; it does not run it, so it cannot show how an application behaves for its users.

Before and after

Did the fix hold?

The same made-up shop, “fixed” two ways. Both comparisons are real results. A problem only counts as fixed when Ctrlflip re-examined the code and it is gone.

Trust & privacy

What happens to code here, in short

  • Samples for everyone, your own code by invitationAnyone can inspect the sample projects. People the site owner invites can also upload their own code to a private workspace, in an early preview.
  • Nothing is runCtrlflip reads committed files. It does not run the project's code, package scripts or tests.
  • No AI service receives anythingThe website sends nothing to an AI provider. Fix instructions are text you copy yourself.
  • Your sample runs are yours to deleteRuns you start are kept for this browser for 7 days, and you can delete them at any time.
Read Trust & Privacy

Limits

Limits and common questions

  • Can I inspect my own project?

    By invitation, during the early preview. Invited people sign in to a private workspace, upload a ZIP of their code and compare versions. The workspace has not had an independent security review yet, so upload only code you are comfortable sharing in an early preview.

  • Does a clean report mean my app is safe?

    No. A report covers the checks listed above, on the files it says it read. It is a reading of the code, not a test of the running application.

  • What does “Couldn't confirm the fix” mean?

    The problem is no longer reported, but Ctrlflip could not re-examine the code where it was (for example, it moved into a folder that is not inspected). It is not counted as fixed.

  • Does Ctrlflip change my code?

    No. It gives you instructions to copy. Your AI builder or developer makes the change, and you inspect the new version to check it.