Skip to main content

vesk

Vesk Verify tests an OpenAI-compatible LLM endpoint with prompt-injection, jailbreak and PII-leakage probes, then renders a report mapped to EU AI Act, DPDP and NIST AI RMF.

Status: alpha (0.1.x). Interfaces may change between minor versions.

Install

pip install vesk-cli

Requires Python 3.10 or newer.

Quick start

vesk init                      # write a commented vesk.yaml
export VESK_API_KEY=...        # the env var named by target.api_key_env
vesk scan                      # run probes, write results.json
vesk report results.json -o report.md

api_key_env holds the name of an environment variable (e.g. VESK_API_KEY), not a file path or the key. vesk does not read .env files; export the variable in your shell (or load your .env first, e.g. set -a; . ./.env; set +a). Omit api_key_env if the endpoint needs no key.

Commands

vesk init

Writes a starter vesk.yaml.

  • --path PATH: where to write it (default vesk.yaml).
  • --force: overwrite an existing file.

vesk scan

Runs the configured probes against the target and writes a results JSON file.

  • -c, --config PATH: config file (default vesk.yaml).
  • --probe NAME: run only this probe; repeatable.
  • --out PATH: results file (default results.json).

Exit codes:

Code Meaning
0 Scan completed; no finding at or above scan.fail_on.
1 At least one failing probe at or above scan.fail_on.
2 Configuration or file error.
3 Incomplete scan: a probe hit endpoint errors.

This makes vesk scan usable as a CI gate.

vesk report

Renders a report from a results file.

vesk report results.json --format html -o report.html
  • --format md|html: output format (default md).
  • -o, --output PATH: write to a file instead of stdout.

Configuration

vesk init writes a fully commented file. In short:

version: 1
target:
  base_url: https://api.example.com/v1   # OpenAI-compatible chat completions API
  model: my-model
  api_key_env: VESK_API_KEY              # name of the env var; never put the key in the file
  # system_prompt: "You are a support bot."
  timeout_s: 30
  max_retries: 2
scan:
  probes: [prompt_injection, jailbreak, pii_leakage]
  samples_per_probe: 20
  max_concurrency: 4
  seed: 0
  fail_on: high                          # none | low | medium | high
report:
  frameworks: [eu_ai_act, dpdp, nist_ai_rmf]
  system_name: "My AI system"

Probes

Probe Checks
prompt_injection Whether text in the user turn or in quoted data overrides the instructions.
jailbreak Whether persona and role-play framings make the model drop its rules. Probes ask only for a harmless marker, never for harmful content.
pii_leakage Whether the model repeats synthetic personal data planted in its own context. Training-data regurgitation is out of scope for 0.1.

Privacy

The API key is read from an environment variable and is not stored in the config. Probe requests go only to the endpoint you configure. PII probes use synthetic values, masked in stored results.

Reports are generated automatically from test results. They are not legal or compliance advice and do not certify compliance with any law, regulation or standard.

Development

pip install -e ".[dev]"
pytest
ruff check .

License

Apache-2.0. See LICENSE and NOTICE.

Metadata

Release files for vesk-cli 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vesk-cli 0.1.3
File Size Uploaded Provenance Actions
vesk_cli-0.1.3.tar.gz 24.3 kB With provenance Details for vesk_cli-0.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for vesk-cli 0.1.3
File Interpreter ABI Platform Actions
vesk_cli-0.1.3-py3-none-any.whl Python 3 none any Details for vesk_cli-0.1.3-py3-none-any.whl

Total release size: 50.3 kB

Release files / vesk_cli-0.1.3.tar.gz

Download URL vesk_cli-0.1.3.tar.gz
Size 24.3 kB
Tags Source
SHA-256 checksum
How to use checksums
36f0d8001d5e09577e3315a8072564a44dfcaeb780b64ebdd3a36542aa9eee13
BLAKE2b-256 checksum
How to use checksums
9ae5d4c0162abc3c33c7a4c99547f21d236f1d165dcff63334c917e48fdc5d19
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

Release files / vesk_cli-0.1.3-py3-none-any.whl

Download URL vesk_cli-0.1.3-py3-none-any.whl
Size 25.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2b533304eaaed68827052a0b0ff76f53782027eddd502003ecc7a4d421a768d9
BLAKE2b-256 checksum
How to use checksums
ec7376ff0e7d2610384c2599d752ed3c6bbf8e673d4c1ef186367e36a5dda48b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

Security for vesk-cli 0.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for vesk_cli-0.1.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page