Testing Hub · Browser beta coming soon

Know what
you’re shipping.

Bring your repository. Run focused checks. Leave with a clearer view of what needs attention.

Getting ready for your first runSee how it works

GitHub sign-in · Private run history · No local installation

A release, reviewed.Example report

Security baseline

  • Secrets kept out of sourcePassed
  • Input validationPassed
  • Session expirationFailed
  • File uploadsSkipped

See the output behind each result. Review skipped checks and decide what to fix next.

From repository to results

A small routine before a release.

01 / CONNECT

Bring your code.

Choose a GitHub repository and branch. Sign-in covers public code; add a read-only token for the private repositories you choose.

02 / CHECK

Give the run a purpose.

Inspect the project, run the 30-control security baseline, or use your own test commands. Every run starts with a fresh, isolated workspace.

03 / IMPROVE

Follow the evidence.

Review the output, revisit private run history, and export a report tied to the exact commit you checked.

The first release

Focused checks.
Clear boundaries.

Made for small Node.js and Python projects that need an easy place to run repeatable checks.

What can I run?

Repository inspection, 30 source-level security checks, npm test, pytest, and saved shell commands. Dependency installation supports package-lock.json and requirements.txt through npm and PyPI.

How is my code handled?

Each job uses a temporary workspace. Repository credentials stay encrypted in the application and are never given to test commands. Results belong to your account; you can export or delete them, disconnect private repository access, or delete your account.

What are the beta limits?

By default: 20 jobs per rolling 24 hours, two active jobs, 10 minutes per job, a 25 MB compressed repository archive, and 30 days of report history. The app displays your current allowance.

Does a passing report mean my app is secure?

A passing result means a check completed successfully. Source checks can miss issues and do not assess every production setting. Review the evidence and skipped checks alongside your release process.

What is outside this release?

Browser testing, native mobile builds, private package registries, and tests that need external services. The runner includes Node.js 22 and Python 3, with network access limited to supported package downloads.