veto-sdk 2.8.5 → 2.8.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -5
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # veto-sdk
2
2
 
3
- [![npm](https://img.shields.io/npm/v/veto-sdk?color=000000)](https://www.npmjs.com/package/veto-sdk)
3
+ ![npm](https://img.shields.io/npm/v/veto-sdk?color=000000)
4
4
  [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](../../LICENSE)
5
5
 
6
6
  TypeScript policy runtime for AI agent tool calls. Veto wraps your tools, evaluates deterministic policy before each handler runs, and preserves the original tool interface.
@@ -26,11 +26,11 @@ const agent = createAgent({ tools: safeTools });
26
26
 
27
27
  ```bash
28
28
  npm install veto-sdk
29
- npx veto init
29
+ npx --package veto-cli@latest veto init
30
30
  node examples/60-second-denied-call/denied-call.mjs
31
31
  ```
32
32
 
33
- `npx veto init` creates blocking local defaults in `veto/rules/defaults.yaml`, so the example deterministically denies `bash` with `rm -rf` before the handler runs. No provider SDK or API key is required.
33
+ `npx --package veto-cli@latest veto init` creates blocking local defaults in `veto/rules/defaults.yaml`, so the example deterministically denies `bash` with `rm -rf` before the handler runs. No provider SDK or API key is required.
34
34
 
35
35
  ## Python parity
36
36
 
@@ -44,10 +44,10 @@ agent = create_agent(tools=safe)
44
44
  ## Local policy
45
45
 
46
46
  ```bash
47
- npx veto init
47
+ npx --package veto-cli@latest veto init
48
48
  ```
49
49
 
50
- The canonical npm package for `npx veto` is `veto`. The `veto-cli` and `veto-sdk` bins remain compatibility paths for existing users.
50
+ For public no-install CLI usage, use the owned `veto-cli` package form: `npx --package veto-cli@latest veto ...`. The unscoped `veto` npm name is reserved/local pending transfer; `veto-cli` and `veto-sdk` bins remain compatibility paths for existing users.
51
51
 
52
52
  ```yaml
53
53
  rules:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "veto-sdk",
3
- "version": "2.8.5",
3
+ "version": "2.8.6",
4
4
  "description": "Policy runtime for AI agent tool calls",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",