Free · one server · no account needed
Free risk assessment for your server
Get a rating and a risk summary by stack without signing up. Stacks are groups of software, for example system (Linux), web server, Python applications. Specific findings for your server, known fixed versions and ongoing tracking are available with monitoring.
Run this on your server
Run the command in the terminal of your Linux server. The script collects software information, pseudonymizes it locally and sends it for checking. Analysis usually takes a few minutes, then a report link appears in the terminal.
curl -fsSL https://patchfirst.dev/check.sh | shRequirements and other ways to run
Python is optional. You need curl and sh; Python 3.8+ with cryptography uses the zipapp, otherwise Linux x86_64 uses a binary. Its SHA-256 is checked against the same HTTPS service: this checks integrity and is not an independent signature. No root access required. An abrupt termination may leave temporary files behind.
Preview data before sending
The command above runs a normal check. With any launch method, --json shows anonymized JSON without sending it:
curl -fsSL https://patchfirst.dev/check.sh | sh -s -- --jsonAlternatively, download the zipapp and run it manually with Python 3.8+. The same flag previews the data:
curl -fsSLo patchfirst.pyz https://patchfirst.dev/agent/patchfirst.pyz &&
python3 patchfirst.pyz check --json --api https://patchfirst.devAfter reviewing the JSON, send the data and get a report link:
python3 patchfirst.pyz check --api https://patchfirst.devBinary without Python
Linux x86_64: download the binary and check SHA-256 before running it. The checksum comes from the same HTTPS service and does not replace an independent signature. For Alpine, replace patchfirst-linux-x86_64 in every command with patchfirst-linux-x86_64-musl. For aarch64, use Python 3.8+ or run from another machine with --ssh.
curl -fsSLo patchfirst https://patchfirst.dev/agent/patchfirst-linux-x86_64
curl -fsSLo SHA256SUMS https://patchfirst.dev/agent/SHA256SUMS
expected=$(awk '$2 == "patchfirst-linux-x86_64" {print $1}' SHA256SUMS)
printf '%s patchfirst\n' "$expected" | sha256sum -c - &&
chmod 700 patchfirst && TMPDIR="$HOME" ./patchfirst check --json --api https://patchfirst.devCheck another server over SSH
Ready-to-run binaries are available only for Linux x86_64 (use the musl variant on Alpine). Download the appropriate variant using the “Binary without Python” instructions. The target Linux server only needs sh; anonymization runs on your machine.
TMPDIR="$HOME" ./patchfirst check --ssh user@host --ssh-opt StrictHostKeyChecking=accept-new --api https://patchfirst.devOn macOS and other systems, use the .pyz: you need Python 3.8+ and an SSH client. Download the script and run the check:
curl --retry 3 -fsSLo patchfirst.pyz https://patchfirst.dev/agent/patchfirst.pyz &&
python3 patchfirst.pyz check --ssh user@host --ssh-opt StrictHostKeyChecking=accept-new --api https://patchfirst.devStrictHostKeyChecking=accept-new saves the key on the first connection and rejects changed keys. Verify the server fingerprint separately before connecting for the first time.
Manual check: preview data before sending
Download the zipapp and print JSON using Python 3.8+. Without Python, use the binary option below.
curl -fsSLo patchfirst.pyz https://patchfirst.dev/agent/patchfirst.pyzpython3 patchfirst.pyz check --json --api https://patchfirst.devBinary without Python
Linux x86_64: download the binary and check SHA-256 before running it. The checksum comes from the same HTTPS service and does not replace an independent signature. For Alpine, replace patchfirst-linux-x86_64 in every command with patchfirst-linux-x86_64-musl. For aarch64, use Python 3.8+ or run from another machine with --ssh.
curl -fsSLo patchfirst https://patchfirst.dev/agent/patchfirst-linux-x86_64
curl -fsSLo SHA256SUMS https://patchfirst.dev/agent/SHA256SUMS
expected=$(awk '$2 == "patchfirst-linux-x86_64" {print $1}' SHA256SUMS)
printf '%s patchfirst\n' "$expected" | sha256sum -c - &&
chmod 700 patchfirst && TMPDIR="$HOME" ./patchfirst check --json --api https://patchfirst.devCopy only the anonymized JSON from standard output. Server names are not sent.
Check your project's lock file
Choose or drop lock files: your browser parses them locally and shows what will be sent for the check. Nothing needs to run on a server. The check covers only dependencies from the file.
What data is used
A script on your server collects a list of software and versions and marks which services are reachable from the internet. IP addresses and real server names are never sent, and paths are replaced with irreversible labels. The data goes to PatchFirst; for matching, names and versions of public packages are sent to OSV.dev without any server identifier. The check is an exact algorithmic match against our vulnerability database: the same data always gives the same result, with no neural networks. A language model only helps fill our vulnerability database from public news. It never works with customer data and never sees it.
Checking now
- Ubuntu
- Debian
- Alpine
- RHEL
- Rocky Linux
- AlmaLinux
- openSUSE / SUSE
- Docker
- Kubernetes
- PHP
- Composer
- Python
- Node.js
- Ruby
- nginx
- Apache
- MySQL
- MariaDB
- PostgreSQL
- Redis
Coming soon
- Windows Server
- Java / Maven
- Go
- .NET
- Rust
What monitoring adds for your server
A check without registration gives a rating and stack risk summary. Monitoring shows specific findings for your server and known fixed versions, notifications in your browser or in Telegram, and access for your AI. First server free. Then $5 per server per month, from paid seat 6: $3, from paid seat 26: $2. Pay yearly and save 20%. The free server gets a fresh report at most twice a day.
- Create an account.
- Get the connection command in the dashboard: your first server is free.
- Run it on your server and wait for the first report.
A one-off check does not enable monitoring.
Reports are available for 7 days. The link includes keys: anyone with it can open the report.