Skip to main content
Starter. For “an AI tool built my app. What should I check before I publish it?”
Many app builders and hosts already scan your app before it goes live. Use that scan. Penthera does not replace it, and we don’t claim it finds more. It is a second check that runs on your own machine or in your own CI. Your code and secrets are not sent anywhere to be checked. That matters more as more of an app is written by tools you can’t see inside. A second, independent check is a safeguard you control.

What your builder already checks

Each row comes from the builder’s own docs, read on 28 October 2026. Builders change these often; if a link says something else, the link wins.

What Penthera adds

  • It runs where your code is. On your laptop or in your GitHub Actions, with no account. A repo scan makes no outside connections (E17 results).
  • It checks your AI tooling too. MCP servers, skills, hooks and pre-approved shell commands in the project, with penthera agents.
  • The same commit gives the same result. Written rules decide every finding, so you can run it again and compare.
  • You can keep the result. --evidence <dir> writes the reports and a manifest with SHA-256 hashes, which penthera evidence verify checks later.
What it does not do: it does not log in to your live app, and it finds known classes of problems, not novel ones. See Privacy and Methodology for the limits.

Check before you publish

Get the code onto your machine first. Most builders sync to GitHub; see App builders for each one.
npm audit lists known vulnerabilities in your npm packages. A default Penthera run can miss those, so run both.
Read the Penthera exit code before you publish: A critical or high finding counts toward exit 1 wherever it is, also in test fixtures or build output. The agent brief lists those under Likely noise, says Review and tells you why the run fails. A key in a file git ignores is reported at low, so it does not fail the run. Penthera tests login and access rules from outside, with rules for known problems. It does not log in to your app unless you pass a session with --auth-cookie or --auth-bearer, and it has no rule for how your payments work.

Make it automatic

  • On every commit: penthera hook install adds a pre-commit hook that checks staged files for secrets, agent config and lockfile changes. See hook.
  • On every pull request: add the GitHub Action. A pull request that the check fails can’t be merged, if you make the check required in your branch settings.
  • After publishing: paste the live URL into penthera.org for a passive check of the public page.