verqen/

One repository · one automated run

Automated code check against a published rule catalog

Verqen checks your GitHub repository against a fixed, published catalog of rules. Every finding names the rule, the condition that triggered it, the file and the line. No person reads your code, and nothing in your repository is changed.

Check a repository

$749 per run

Up to 400 source files per repository

Verqen rule check · demo repositoryDEMO
Read the rule catalog →
01

Pay

Pay $749 in cash at the registered cash register location in Tbilisi, Georgia, against a receipt.

02

Open your link

You receive a one-time link. Connect the Verqen GitHub App to one repository and start the run.

03

Read the Check Run

The result appears as a GitHub Check on the latest commit of your default branch.

Who's behind Verqen

Verqen is built by German Kosach, an engineer with a Swiss MBA. The check engine is source-available — you can read exactly how every rule is detected.

Check engine on GitHub →[email protected]German Kosach on LinkedIn →

Frequently asked questions

What is Verqen?
An automated check of one GitHub repository against a published rule catalog. Each finding names the rule it triggered, the condition, the file and the line.
What do I get?
A GitHub Check on the latest commit of your default branch with every triggered rule. The run includes no code changes, and no person reads your code.
How much does it cost?
$749 per run, paid in cash at the registered cash register location in Tbilisi, Georgia, against a receipt. One run covers one repository with up to 400 source files. Binary, generated, lock files and files over 256 KB are not counted.
Does my code leave GitHub?
The engine reads the repository archive in memory and does not store your code. Only the triggered rules, conditions and locations are kept.
Who can order?
Individuals who live outside Georgia.