Skip to content

Releases: veto-protocol/veto-cli

Release list

v0.5.7 — Launch-readiness pass

v0.5.7 — Launch-readiness pass Latest
Latest

Choose a tag to compare

View all tags
@tomermeirovich tomermeirovich released this 03 May 10:37
v0.5.7
3962876

First publicly-launched release. Fixes friction discovered during dogfooding + production-grade polish on visible CLI surfaces.

Highlights

  • No more SSL errors on macOS Homebrew Python. The CLI now uses certifi for its trust bundle and explicitly passes an SSL context to every urllib call. Fixes the long-standing CERTIFICATE_VERIFY_FAILED that hit Homebrew-installed Pythons.
  • Banner upgrade. The CLI banner shown on veto register / veto authorize is now the full chafa-rendered Veto wordmark — matches the install.sh banner exactly. No more box-drawing seams in monospace fonts.
  • Authorize output now shows the engine's actual work. Each call surfaces engine version, reason codes (machine-readable), policy fingerprint with content hash, transaction ID, and a signed-receipt summary block (decision_layer, input_fingerprint). The verify command remains the cryptographic ground truth.
  • Smarter register examples. The 'Try it' commands shown after veto register now pull from the actual policy: approve example uses the first merchant from the allowlist, deny amount is 2× the per-tx cap (so the deny output stays clean — only 2 reason codes fire instead of 5).
  • License: MIT → Elastic License v2 (ELv2). Free to use, modify, embed. Not free to host as a managed service to third parties.

What's required to upgrade

~/.veto/venv/bin/pip install --upgrade veto-cli

Or wipe and reinstall via the curl one-liner:

rm -rf ~/.veto
curl -fsSL https://veto-ai.com/install.sh | bash

What's open

  • The APPS schema (github.com/veto-protocol/x402-policy-schema) stays MIT — invites external implementers.
  • This veto-cli engine is the reference implementation under ELv2.

Try it

veto register --preset inference --email you@example.com
veto authorize --amount 0.05 --merchant api.openai.com --action payment
veto authorize --amount 10 --merchant amazon.com --action payment

You should see APPROVED on the first, DENIED with two reason codes on the second.

veto-ai.com · github.com/veto-protocol

Assets 2
Loading