Security, explained in plain words.

Start here What this wiki is, who it is for, and the first few pages to read depending on how you built your app. 4 min Why Sentrint exists AI and no-code tools ship working apps with real security holes. Sentrint gives non-security builders a fast, honest read on what is exposed. 4 min FAQ & glossary Straight answers to the questions founders ask before running a scan, plus a plain-English glossary of the security terms you will see in a report. 5 min

How a scan works What happens from the moment you sign in to the moment you get a report. Sign in, pick a repo, get a score, a grade, findings and a fix prompt. 4 min Reading your report What the score, the letter grade and the severity levels mean, what to fix first, and how a rescan confirms a fix is really gone. 5 min The fix prompt Every finding comes with a copy-paste fix written for your AI builder, in small steps, so the tool fixes one thing at a time instead of rewriting your app. 5 min Inside the security engine How the scan works under the hood, the rule families it runs, the AI review layer that filters false positives, and how findings get scored. 6 min Sentrint for developers The severity model in detail, the fix-and-rescan workflow, the embeddable security badge, and where this fits alongside code review and CI. 5 min Plans and what they include Start free with one scan a month. A 6-scan pack unlocks the full report and fix prompts. Founder gives you 36 scans a month. Plain pack totals only. 5 min

Security for AI-built apps Why apps built with AI tools and no-code platforms get breached, and the handful of holes that show up again and again. 5 min Common vulnerabilities, explained A plain-English tour of the security holes that show up in AI-built apps, what each one is, how it happens, and what a finding looks like. 9 min

Your code and your data Your source code is never stored. Here is exactly what a scan reads, what we keep, for how long, and the rights you have over all of it. 5 min